Improving performance

For best performance, FileMaker Server should be run on a dedicated machine reserved for use as a database server. When FileMaker Server is hosting many clients or a large number of database files, it uses a high level of processor, hard disk, and network capacity. Other processor-intensive software or heavy network traffic on the same machine will cause FileMaker Server to run more slowly and degrade the performance of FileMaker Pro on client machines.

  • Do not use antivirus software to scan the folders that contain hosted database files or progressive backup folders.
  • Avoid installing FileMaker Server on a machine that is a user’s primary workstation or network file server.
  • You cannot run two different versions of FileMaker Server on the same machine at the same time.
  • Avoid using the machine running FileMaker Server as an email, print, or file server.
  • Do not use system backup software to back up databases hosted by FileMaker Server. Instead use the FileMaker Server Admin Console to schedule backups of databases.
  • Specify a progressive backup folder on a different hard drive than the one where the hosted databases reside. Since the progressive changes may be written to the progressive backup folder at nearly the same time that changes are written to the hosted databases, using two different hard drives may improve server performance.
  • Consider disabling startup restoration if server performance is an issue. See Understanding startup restoration.
  • Disable screen savers and sleep (or hibernate and standby) mode on the server. These operating system features reduce performance or suspend access to hosted databases.
  • Use a fast hard disk, a multiple-disk RAID (redundant array of independent disks) system, or a reliable Storage Area Network (SAN) for the hosted databases.
  • Make sure there is enough free disk space on the system drive of the master machine to store the temporary files. The Database Server creates temporary files in a temporary directory on the master machine to cache data for hosted files. The Database Server creates one temporary file for each open hosted file, and automatically closes and deletes the temporary file when the associated hosted file is closed. In most cases, the size of the temporary file is 10-20% of the size of the associated hosted file, but the actual percentage depends on the number of clients and server-side scripts and their activity level. The Database Server periodically checks the temporary file size and will shrink a temporary file if it grows too large compared to the amount of free disk space.
  • Turn off file indexing—in Windows, Indexing Service; in macOS, Spotlight; or any other third-party file indexing software. This feature reduces performance.
  • If you have many FileMaker WebDirect clients, consider switching to a multiple-machine deployment. See FileMaker Server Installation and Configuration Guide.
  • If possible, schedule tasks to run when clients are less likely to be using hosted databases.
  • Request for app developers to limit the use of the Perform Script On Server script step in hosted databases so that scripts run on the client machines rather than on the server machine.

Notes  

  • Because some DHCP servers cycle IP addresses, use a static IP address.