Administrator’s Guide

Chapter 5
|
Configuring FileMaker Server 35
By default, the cache flush mechanism will attempt to scan the entire
cache in a minute. In most cases this means all cached changes on the
server will be no more than one minute old, although database size and
hard disk speed can affect these results.
To change this behavior and spread the cache flushing over a longer
period of time, select
Distribute cache flush over (hh:mm). Unsaved
changes in FileMaker Server will be no older than the interval you
specify. FileMaker Server reduces the amount of data to inspect every
second to a smaller value, down to 128k per second.
This property determines how much cache is flushed each second.
Before deciding to change this property the administrator must
balance cache size against the risk of data loss in the event of a
computer failure. Locations that require maximum performance and
are less concerned about the potential for lost data can use a longer
cache flush distribution interval, while locations that want maximum
data integrity should use a smaller cache flush distribution interval.
For example, if the value is set to 10 minutes with a 64MB cache, the
engine will inspect 1/600th of the cache each second, or about 110K
of cache, (less than the minimum, so the engine will actually inspect
128K of cache) and write only the changed data to disk. However, if
this interval is set to 10 minutes with a 500 MB cache, it will only
inspect 853K as opposed to the default value of 1/60th of the cache, or
8.5 MB. Used this way, the server can distribute its disk writing over
time, and therefore allow the server CPU a higher priority to service
client requests, as it will take much less time to inspect 853K
compared to 8.5MB.
Opening runtime solutions automatically
Runtime solutions are database files created in FileMaker Pro
Advanced that are typically used with a dedicated, “bound” copy of
the FileMaker
Pro application. If you host runtime database solutions
created by FileMaker Pro Advanced, you can enable FileMaker Server
to automatically open runtime solutions when FileMaker Server
starts, provided runtime solutions are stored in one of the designated
locations. See
“Starting FileMaker Server (Windows)” on page 45 for
more information.
If the runtime solutions do not have .fp7 filename extensions, you
must register their filename extensions in FileMaker Server.
Windows: Configure runtime solution properties in the Database
Hosting
assistant or select host and then choose Action menu >
Properties > Runtime Solutions tab.
Mac OS: To configure runtime solution properties, choose View
menu > Configure, then click the Runtime Solutions tab.