"File Cache" function cause performance problems on some servers
Created: 12 Feb 2013 | 5 comments
We have the following configuration for the "File Cache" function for our servers with SEP 12.1.2 installed:
- Enable file cache [x]
- Use the default file cache size [x]
- Rescan cache when new definitions load [x]
Now we see on some servers a performance impact when new definitions get loaded.
- On one SQL Server the "Rescan" only takes ~4 Minutes - C:\ drive kind of busy but not too much really – I see this as a normal impact with the “Rescan” option enabled
- On another SQL the "Rescan" takes up to 30 Minutes and scans 15.000 files - C:\ busy the whole scan time
- Archiving server that stores millions of files the "Rescan" can take up to 60 Minutes - D:\ drive (where the archived PDFs are stored) is very busy with some performance impact to search query’s from the archiving solution
My questions are now:
- Should we disable the “Rescan cache when new definitions load” function on all servers?
- If so, is that a security risk?
- Let´s say a “bad file” is marked as clean inside of the cache
- New definitions get loaded that “know” that the “bad file” should get detected
- Will it get detected then?
- How big is the “default cache size”? Can it be changed in SEP12.1? The documentation says “Applies only to legacy Clients” Do they mean SEP11?