Selecting the right hardware

Before you select hardware for the server, consider how many users are or will be accessing the server. If many users are accessing the database, then the hard drive and processor will probably get heavy usage. A Database Server accessing a great deal of data can take more resources and needs the right equipment.

Consider these key areas when selecting the hardware:

  • Disk subsystem: The disk subsystem is a type of disk storage that has an integrated collection of disk drives. This subsystem is the most important factor to consider when purchasing hardware for FileMaker Server because it reads and writes data stored in the database. Having a fast and optimized disk subsystem to effectively handle both reading and writing the data has a significant impact on how the database performs. Regardless of the specific drive type you selected, configure the subsystem to support a Redundant Array of Inexpensive Disks (RAID) or reliable Storage Area Network (SAN) for the hosted databases.

  • Processor: FileMaker Server handles many processor intensive operations, such as finding information, evaluating unstored calculations, and resolving relationships; therefore, the processor you choose is almost as important as the disk subsystem. Because FileMaker Server can take advantage of multiple processors, certain database tasks can be handled by different processors.

  • Network: The network throughput can be measured using various tools on the system, and the quality of network throughput depends on several factors. These include the type of Network Interface Card (NIC) installed and the network's physical infrastructure. While the network infrastructure may be outside your control, problems happen due to the network configuration, traffic, and routing. Users can connect to and work with databases over a LAN or a WAN connection. Connecting to a FileMaker Server hosted database over the internet or a WAN requires that several ports be open for TCP.

  • Memory: The amount of memory a database uses depends on the size of the database, the type of database, the number of users, and the database's complexity. Any one of these factors can require more memory. Another critical factor for FileMaker Server is the cache.

    The maximum allowed database RAM cache size is the smaller positive number of these two formulas:

    • the physical RAM size minus 1024 MB (1 GB)

    • 90% of the physical RAM size

    If web publishing is enabled in a single-machine configuration, set the database cache to no more than 50% of the maximum.

    Specify the database cache size using the CLI command set serverconfig cachesize. For example, to set the cache size to 1024 MB, use the command fmsadmin set serverconfig cachesize=1024. See CLI Help.

Note  During deployment, FileMaker Server configures memory use based on the physical RAM size. If you add or remove RAM, you need to change the cache size manually using the CLI command or reinstall FileMaker Server so that FileMaker Server can recalculate optimal memory use for its components.

Virtual servers

Virtualization lets you run multiple instances of an operating system and its specific applications or services on the same physical hardware because you can use a software application to divide a server into isolated virtual environments. Some IT departments turn to virtualization to reduce costs and as a way to use the full potential of the hardware.

FileMaker Server has been tested to run in virtual machines. When using FileMaker Server within a virtualized environment, you must monitor the machines to determine the stress being placed upon the physical hardware.