New answers tagged cache
For what it's worth, I am seeing the same issue with version 3.3.4 and it appears that this post in squid-users is describing the same problem with 3.2.1. I've noticed that it seems to work with 3.1.10 (which is installed by default with my package manager). By analyzing the logs I was able to determine that the hash lookup key used during the store (i.e. ...
You could try to disable caching credentials by adding directive to /etc/sssd/sssd.conf: [domain/default] cache_credentials = False You may then verify that sssd uses cache on credentials with console command: # authconfig --test|grep credential credential caching in SSSD is disabled
You can't disable caching completely with sssd. You can disable sss as an authentication provider completely and just query LDAP directly if that's what you want. For example, in /etc/nsswitch.conf, change lines like: passwd: files sss to passwd: files ldap You can force cleaning of the cache by removing /var/lib/sss/db/*
I've had some scenarios were updating statistics with FULLSCAN on key tables has forced data into cache and made my subsequent DMLs around those tables a lot faster. And this was not a result of out of date statistics as it resulted in no changes in the execution plans.
You can lock a particular directory (or files) into the filesystem cache/VM subsystem by using the vmtouch utility. Example: Daemonise and lock all files in a /var/app/data into physical memory: vmtouch -dl /var/app/data
I think mod_cache doesn't work out of the box, so you should tweak your apache httpd config or vhost config: First on the Directory where the static files are located you would want to set: <FilesMatch "\\.(|pdf|jpg|jpeg|png|gif|)$"> Header unset Last-Modified </FilesMatch> Also in your cache_mod config as far ...
Top 50 recent answers are included