perfGenie is a Salesforce open-source solution for continuous, low-overhead contextual profiling of Java services. It parses Java Flight Recorder (JFR) profiles — produced by JMC, async-profiler, or jcmd — and thread dumps, and renders them as calling context trees, a samples explorer, flame graphs, thread state, river, and experimental 3D hotspot surface views. Two profiles.
About
perfGenie is a Salesforce open-source solution for continuous, low-overhead contextual profiling of Java services. It parses Java Flight Recorder (JFR) profiles — produced by JMC, async-profiler, or jcmd — and thread dumps, and renders them as calling context trees, a samples explorer, flame graphs, thread state, river, and experimental 3D hotspot surface views. Two profiles can be diffed via context-tree or flame-graph compare views, and profiles can be filtered by custom event context, thread id, or thread name, with request and metric timeline views built on custom events. Deployed as a server it watches a directory for incoming JFR files and stores parsed data through Cantor in H2, MySQL, or S3, and an aggregation feature combines profiles over longer periods. It analyzes profiles rather than generating load, so it complements load generators during performance test runs.
Best for
Results Analysis scenarios across typical web and service stacks
Teams that prefer open-source licensing and self-hosting options
Groups comfortable scripting in Java
Not the best fit when
Teams unwilling to operate generators, results storage, and scaling
Architecture and concurrency
perfGenie is commonly operated as self-hosted software with scenario authoring in Java. Concurrency and distribution depend on how you size workers or injectors.
perfGenie is best for engineers designing load, stress, and performance tests for web and service systems. It is open source, so teams can self-host and extend it. Vendor: Salesforce. Deployment model: self-hosted. Free; BSD-3-Clause license. Confirm details against the official site and a short proof-of-concept in your environment.
How does perfGenie differ from JMeterHub?
Compared with JMeterHub, perfGenie is open source while JMeterHub is freemium; deployment is self-hosted versus cloud for JMeterHub; scripting centers on Java rather than None. perfGenie lists protocols None; JMeterHub lists None. Status is active versus active. Use the Test Rig to compare full specs side by side before a proof-of-concept.
What scripting language and concurrency model does perfGenie use?
perfGenie uses Java for scripting or scenario definition. Runtime model: code-first scenarios where virtual users execute scripted behavior under load. OS support: Windows, macOS, Linux. Protocols: None. Match these to how your team already authors tests and which systems you must drive under load.
What is the cloud or enterprise path for perfGenie?
perfGenie is primarily self-hosted; teams typically run generators on their own machines, CI runners, or private cloud. Plan for generator capacity, network access to targets, and result storage yourself. As open source, commercial support or hosted siblings may exist separately. Check the official site. Pricing note: Free; BSD-3-Clause license.
What are known limitations of perfGenie?
perfGenie limitations to weigh: self-hosted tools require you to provision, scale, and observe load generators yourself. Status: active. Always validate against your target protocols and scale with a proof-of-concept. Confirm details against the official site and a short proof-of-concept in your environment.