Knowledgebase

Slow FileMaker performance usually comes down to a handful of causes. Here is how to identify which one you are dealing with.

Geographic distance from the server

FileMaker is sensitive to network latency — every record load and script step requires a round trip to the server. If your users are far from your chosen data center, this adds up quickly.

• Quick fix: Migrate to a data center closer to your users (we have 14 regions worldwide)
• Best fix for remote teams: Try our FileMaker Pro RemoteApp service — FileMaker Pro runs right in the data center, so database operations are near-instant regardless of where your users are located

Server memory is running low

When your server's RAM fills up, FileMaker slows dramatically and becomes prone to crashes.

• Check your memory usage in the FMPHost dashboard
• If it is consistently above 80%, an upgrade is likely needed
• Memory upgrades are one click and prorated — you only pay for what you use

Disk space is nearly full

A nearly-full disk causes both performance problems and backup failures.

• Check disk usage in your dashboard — we will alert you before you run out, but act sooner rather than later
• Disk upgrades are independent of memory and take effect after a brief restart

Too many stale connections

If users frequently close FileMaker without logging out, stale connections accumulate and consume server resources. Go to Clients in the Admin Console and disconnect any idle sessions.

Database may benefit from a tune-up

Large databases with a long history can accumulate fragmented storage over time. A FileMaker Recover + Clone cycle rebuilds the database structure cleanly. Contact support for guidance on this process.