This last setting handles how FileMaker Server saves the cache to the hard disk. FileMaker Server cycles through the cache continuously, once per second to be accurate and FileMaker Server doesn't blindly save the whole chunk of the cache it is looking at. It actually inspects the chunk and only saves the changes. The setting here determines how long it takes to complete one full cache saving cycle. So setting it to ten minutes does not mean dump the whole cache to the desk at the end of every ten minutes. It means that FileMaker Server will save ten percent of the cache in the course of one minute. So it will inspect one six-hundredth. That's ten minutes times 60 seconds at a time. It is obvious then that the longer you make this period, the less busy FileMaker Server will be writing to the hard disk. The default setting is one minute. Depending on the size of the cache and the machine specifications, this may be too quick and could affect performance since the cache flush keeps both the processor and the hard disk busy. On the other hand, it's a very safe setting. If a crash were to happen, you wouldn't lose many unsaved changes. Like with many other FileMaker Server settings, it's a trade-off between performance and prudence. Another way of looking at it is this: no saved data will ever be older than the interval that you specified here.