Are there any pros or cons to deleting the cache.ndk before each client startup?
tia
Subject: The con is that you get more traffic
It is used to cache design elements, if you delete it all the time, you end up with more traffic (and server load and potentially waiting time for users) as they have to get cached again.
I would not be aware of a customer doing it all the time. Being a developer, and loading way more burden on this file as any other type of user, I see no use in deleting this file more than once a month, and I would not be aware of any customer deleting the files at all if there is no problem.
Subject: Deleting cache advantages
I understand all the arguments that were put forward here but one thing I noticed is that the cache file has a very bad tendency of growing to 30mb or slighly more and then we see all sorts of problems… From Databases not opening to pointers going wrong.Deleting the cache is not our #1 solution although most of the problems come when it is at or close to 30mb…
R8.5(1) designer will also throw a bunch of errors when the same condition comes…
Perhaps clearing the cache at restart is not really the solution but how about clearing it once a week or clearing it before it reach the critical 30mb point?
Jacques
Subject: Agreed with above - except if it is on file server
if the cache6.ndk is located in the notesdata folder residing on a fileserver, the design elements get pushed/pulled twice via the network. In this case it might be a better solution to relocate the file via the notes.ini parameter Cache= to a CPU-local HD.In WTS/Citrix environments it is not persitance in the user’s TEMP folder and will get automatically removed after user logged off.
Subject: Potential unread mark problems
Deleting the cache.ndk every day may also impact unread marks since the unread mark journal is stored in the cache.ndk. The unread mark journal mostly comes into play when there is more than one replica and you are not configured to replicate unread marks via the database property.
Subject: That’s good information
I didn’t know that. I will keep that in mind when dealing with cache issues.
Subject: Agreed - network traffic increases
sometimes dramatically…have measured onsite before - increases the network traffic between the client and the server.
Subject: Somewhat limited benefits
You will see a degradation of database performance by deleting your cache.ndk every time you start Notes. The cache.ndk stores forms, subforms, scripts and other design elements for databases. If there is corruption that you are trying to deal with you would be better served to root out the cause rather than start with a new cache every time you launch Notes. One thing you can try if you are experiencing issues is to open the cache.ndk manually, then go to the ByURL view and delete the contents of that view. That can help many times with cache issues.
Cheers