# FileMaker/FMS stress testing tools?

**URL:** <https://the.fmsoup.org/t/filemaker-fms-stress-testing-tools/5392>\
**Category:** Questions\
**Tags:** community\
**Created:** [April 28, 2026, 10:32am UTC](https://the.fmsoup.org/t/filemaker-fms-stress-testing-tools/5392 "2026-04-28T10:32:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [April 28, 2026, 10:32am UTC](https://the.fmsoup.org/t/filemaker-fms-stress-testing-tools/5392/1 "2026-04-28T10:32:36Z")

</div>

For APIs, I generally use either Apache JMeter or (for Python), Locust to stress test.

Wanted to know what folks use to stress test FileMaker/FMS apps for 50, 100, 500 users.

Thanks,

---

<div class="post-metadata">

**Author:** ![steve\_ssh](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steve_ssh/32/160_2.png) [@steve\_ssh](https://the.fmsoup.org/u/steve_ssh)\
**Post date:** [April 28, 2026, 2:27pm UTC](https://the.fmsoup.org/t/filemaker-fms-stress-testing-tools/5392/2 "2026-04-28T14:27:29Z")

</div>

At least a couple of community members have put some dedicated work/thought into stress testing. What immediately comes to mind is the work that Wim Decorte put into a tool named "Punisher". I have not personally used it, but knowing the high level of quality that Wim puts into everything that he does, I have no hesitation in recommending checking it out.

Of note is that, per the notes about Punisher, I believe that it is a tool which aims to measure the capacity/effectiveness of a _server installation_, as opposed to a tool which aims to measure the same qualities for a particular FileMaker _solution_.

> **[Introducing Punisher](https://www.soliantconsulting.com/blog/introducing-punisher/)**
>
> Learn more about Punisher a tool to help you figure out the impact of your FileMaker Server deployment decisions.

> **[GitHub - soliantconsulting/fm-punisher: Punisher is a tool to test your FileMaker Server's...](https://github.com/soliantconsulting/fm-punisher)**
>
> Punisher is a tool to test your FileMaker Server's performance and benchmark it against different versions of FMS and different machine configs.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [April 28, 2026, 8:45pm UTC](https://the.fmsoup.org/t/filemaker-fms-stress-testing-tools/5392/3 "2026-04-28T20:45:48Z")

</div>

@OliverBarrett, would you say more about the type of testing that you are performing when you use these tools?

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [April 29, 2026, 10:34am UTC](https://the.fmsoup.org/t/filemaker-fms-stress-testing-tools/5392/4 "2026-04-29T10:34:56Z")

</div>

We are just trying to measure how many users our FileMaker application can use with reasonable performance.

Yesterday, without any special configuration our REST service on the server was easily handling 1,000 simultaneous connections with 0.25 seconds per request (using the free LOCUST python testing tool) with no errors. We could add multiple Tomcat installs with a front-end load balancer for multiples of 1,000 connections if needed.

However, .... when we tested REST endpoints that hit the FMP database, our performance quickly plummeted after about 50 users.

Since we may need to massively scale our application, we're currently planning a migration to PostgresSQL for this app.

Thanks,

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [April 29, 2026, 10:37am UTC](https://the.fmsoup.org/t/filemaker-fms-stress-testing-tools/5392/5 "2026-04-29T10:37:33Z")

</div>

Awesome, Steve. Thank you.
