Just wondering if anyone has seen a real world benefit to increasing the default value for the cache size on Windows or the Mac OS.
Also, whether there is any advantage to saving the cache at specific intervals, rather than "during idle time".
1) yes, some scripts continue till end instead of bombing filemaker
2) specific intervals is dangerous in hosted situations.
I would be interested in knowing what settings for these preferences have been the most successful for other Windows and Mac users.
Hmm, that's interesting. I have only increased the cache size on the server. Could you eleborate on the bombing and cache size? If I understand correctly increasing the cache size prevented crashing FileMaker with certain scripts? If so, I guess there memory management is better than I/O management :-)
I know there is encryption/decryption going on from file cache to memory cache. So if mem cache is large enough less time would be spend encrypting/decrypting, maybe that routine has a mem leak.
For me, increasing FM Pro's cache from 128 to 512 has stopped bombing a specific script under particular circumstances on a couple of client machines. YMMV.
can you expand on what the script was doing? Imports? Bulk operations?
Typically I have found that trying to increase the client cache was more of a short-term band-aid than anything else. In what I found, by making changes to the system the client's use of resources can be made more efficient.
Retrieving data ...