The two directories are found side-by-side. The location varies by CMS; see below. Note that you'll need access to your server's file system. If you have FTP/SFTP/SSH access, you can use that. If you have a control panel, check for a "File Manager" plugin:
So, only the civicrm click-through requests are grinding the VM/Server?
I am not seeiing how to cache those without breaking the counter functionality.
Is site OK when not using the click-through functionality? To make 100% sure that those are the cause, and not some other Varnish config (like not caching when certain session cookies are available).
If it ...
For me, the only way to deal with this problem was to remove as many smart groups as I could from the system. In the process I also rewrote all the dashlet reports I could into Drupal views. There are a few dashlets left that are CiviCRM reports and still rely on smart group. I believe that people who use these reports still have problems with data "...
We have a very similar setup, with the smart group cache timeout set to 0. We also get a lot of deadlocks, but ours are with civicrm_group_contact_cache. They're a mixture of delete, insert, insert ignore, and create temporary table.
Like you I can't quite understand what's happening, or why it results in a deadlock (why doesn't it just queue?). And I'm ...
I cant answer everything but I think I can help clarify a few things;
How can there be a difference between when the cache is flushed and when it is built, anyway? Surely refilling the cache means first you flush it, then you fill it. They cannot be separate
The answer to this lies in the state of the cache, there are in fact two states;
Current - does ...
Caching methods can be enabled or disabled in your CiviCRM settings file (eg: civicrm.settings.php).
The setting you're looking for is:
To disable caching, change the value to 'NoCache'. Other possible settings are documented above the setting in the file.
There is a page about caching in the documentation here: https://wiki.civicrm....