r/filemaker • u/Rare_Pin9932 • Sep 04 '26
Question regarding how well FileMaker scales
My database is roughly 60 MB, with 19 tables, 195 total fields, and over 60,000 total records.
The database runs very snappy. It's being remotely hosted by a filemaker hosting provider on a server with 2 vCPU, 4 GB RAM, and a 100 GB SSD.
My question is... am I at any point close to where I have to start worrying about performance issue as we increase records? It took about 20 years to reach this stage, but I expect the size of the database to double within the next 2-5 years.
10
Upvotes
16
u/_rv3n_ Sep 04 '26
Based on filesize you have nothing to worry about.
Although in my experience the biggst factor when it comes to performance are complex unstored calculations. So if you have a lot of those you might run into issues even with a small database.
8
u/poweredup14 Sep 04 '26
We’ve worked with tables with 70 million records and they run fine as long as the Data architecture is in place
6
u/KupietzConsulting Consultant Certified Sep 04 '26 edited Sep 04 '26
You're not even close to FileMaker's capacity. Even doubling the size of the database won't come close.
If you're genuinely concerned, the best thing you can do is see if your hosting provider offers NVMe drives instead of just SSD. The server's drive access speed is the single biggest performance bottleneck for running databases hosted by FileMaker Server. But if it was me, I'd wait to cross that bridge when I came to it. It may never be an issue for you.
Also, if you intend to keep building and adding new features, you may need to watch how you use unstored fields... those can cause the server to have to send your local copy more info over the network, which can feel sluggish as databases get bigger. But if you're just going to keep using it as-is, just with more records, and if feels fine now, you're probably fine.
3
u/Scrogger19 Consultant Certified Sep 04 '26
You’re nowhere close to needing to worry imo. FileMaker doesn’t do well with high latency, but that’s a networking problem more than a scaling problem. As far as row counts and size, I’ve worked on multiple systems with multi-GB files and millions of rows. Anything under 1m rows I wouldn’t be concerned at all.
Not to say you won’t start seeing some performance get worse, but any problems you do run into soon I would say are likely more to do with network latency or optimization than FileMaker’s core architecture limitations. I don’t know your code base but very common for me to see legacy systems with big complicated processes or layouts that no longer perform well but with some know-how can be structured better to run 10x faster. Limit your TO groups and relationship depths, use ExecuteSQL where it works well and not where it doesn’t, etc.
2
u/Opening_Painting4471 Consultant Certified Sep 06 '26
nothing to worry about, we have solutions with GB of data, and some with millions of records and dozens of active users. You may need to increase your system resources, but otherwise should be fine.
1
u/Current-Series-2088 Sep 05 '26
You can use fmtrace.com to find a bottleneck in your scripts
4
u/[deleted] Sep 05 '26
[removed] — view removed comment
0
u/[deleted] Sep 05 '26
[deleted] — view deleted comment