FileMaker Server performance tuning: cache, connections, and threading
ExpertIdentify and resolve FileMaker Server performance bottlenecks by tuning cache size, concurrent connection limits, and PSOS thread counts.
What you'll learn
- How to read Stats.log to diagnose the root cause of performance problems
- How to size and tune FileMaker Server's database cache
- How to limit concurrent PSOS scripts and optimize their design
FileMaker Server performance is determined by hardware capacity, cache configuration, and the number of concurrent operations it handles. Most performance problems fall into three categories: insufficient cache (causing disk reads), too many concurrent operations competing for CPU, or unoptimized scripts running server-side.
Diagnose using Stats.log
Enable Stats.log in Admin Console → Configuration → Logging. Set the interval to 30 or 60 seconds. After a busy period, download and review the log. Key columns: Cache Hit Percentage (below 90% = undersized cache), Elapsed Time (consistently high = CPU-bound), and Connects/Disconnects (high churn = connection pooling issue). Address the bottleneck the stats reveal before making other changes.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo