Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
No, the clear cache adminapi routine we have on our other intranet system is scheduled to run at certain time intervals. The CF Directory Watcher event sounds impressive. However, I'm not sure how it would perform on my system which contains ~35000 CF templates.
It would be nice to know if Adobe somehow changed the underlying implementation of sandbox security from CF7 to CF8 as performance was never an issue with CF7.
Erick
Copy link to clipboard
Copied
Sure, and like I said, it would be good to get to the bottom of the problem, but before concluding that it's necessarily about CF8, since the trusted cache helped a little, can you tell us what you see as the template cache hit ratio (per the server monitor, or Admin API). If anyone there is averse to the Server Monitor, note that you don't need to turn on any of the "start" buttons (monitoring, profiling, or memory tracking).
Just look at the "Template Cache Status" page (under the "Request Statistics" section in the Statistics tab). I wonder if it may be sub-optimal (meaning, other than 100%). Be sure to look at it after the server's been up and running and had lots of typical traffic. Let us know what you see.
As for your observation about the effect of the directory watcher with a large number of templates, I've not heard it to be a problem. When the directory watcher came out in CF 7, many had the same concern and I seem to recall assertions that it shouldn't matter how large the directories were that were being watched. Are you willing to try it? Again, it was an answer to the concern that your developers didn't like the trusted cache option. If enabling it solves this problem, even if only some, it just seems worth at least trying.
But beyond that, let us know what you see going on in the template cache. I wonder if you may have a problem related to the loading and unloading of templates (going back to the original observation about the JVM, but looking at it more from a CF internals perspective than from a JVM perspective.)
There's got to be an answer (and something unique about your setup), as I've not heard it being a general problem (that wasn't solved by the JVM update).
As always, just trying to help.
Copy link to clipboard
Copied
Sorry for the delay in responding. The "Template Cache Hit Ratio" averaged ~99% when Trusted Cache is enabled.
So I set up the Cache Clear method for testing and it's not going to come close to satisfying our needs. I'm not exaggerating here, but it's literally going to take hours for each sweep. We have ~3500 folders in the root directory it has to search. Again, using the process monitor tool, the jrun process is literally traversing down to each file to read it. This behavior occurs when Sandbox Security is enabled.
So I'm back to Sandbox Security implementation in 8 perhaps being somewhat flawed, at least in our infrastructure. Our content resides on a NetApp FAS3050.
Erick