MyPerf4J
High performance Java APM. Powered by ASM. Try it. Test it. If you feel its better, use it.
Runs with mockssource: GitHubJavaBSD-3-Clausecommit 984684270482
Java, BSD-3-Clause licensed. The project labels itself: agent, apm, bytecode, diagnosis, java agent, jvm monitor, metrics and microservices.
MyPerf4J runs, with stand-ins for the services it depends on. An Argusic agent installed it in 16 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The MyPerf4J Java project builds with Maven and all 75 unit tests pass (62 in MyPerf4J-Base, 8 in MyPerf4J-Core, 5 in MyPerf4J-ASM). The ILoggerTest was fixed to initialize config properties, and a mock InfluxDB v2 server was started for the InfluxDbV2ClientTest.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- ILoggerTest fails with "MyProperties is not initial yet!!!" because it does not initialize MyProperties before calling loadMetricsConfig()3 minutes
- InfluxDbV2ClientTest fails because it tries to connect to a real InfluxDB instance at 127.0.0.1:8086 which is not running2 minutes
- Install time
- 16 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- mvn test exited 0; 75 tests passed across 3 modules (MyPerf4J-Base:62, MyPerf4J-Core:8, MyPerf4J-ASM:5), 0 failures, 0 errors
- Model tokens used
- 161,876
- Exact commit tested
- 984684270482
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Result:** tokens used 161,876 Well done. Here's the final summary of everything we accomplished. **What was done:** 1. **Environment**: Downloaded and configured OpenJDK 17 (Temurin) and Maven 3.9.9 (no `apt`/`sudo`… 2. **Build**: `mvn clean package` succeeded, producing `MyPerf4J-ASM-3.6.0.jar` and other artifacts 3. **Test failures found & fixed**: - **`ILoggerTest`** — failed with `IllegalStateException: MyProperties is not initial yet!!!`. F… - **`InfluxDbV2ClientTest`** — both `testWrite` and `testClose` failed because the test tries to… 4. **Verification**: Full test suite passes — 75 tests across 3 modules, 0 failures, 0 errors **Result:**
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed BSD-3-Clause, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 16 minutes to install, slower than the median of the 137 comparable projects Argusic has measured.
Of the 138 agent projects Argusic has installed and timed, MyPerf4J was the 108th fastest to reach a running state, and 92 of 138 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.32 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.10 |
Topics (from GitHub)
agentapmbytecodediagnosisjava-agentjvm-monitormetricsmicroservicesmonitormonitoringmonitoring-toolobservabilityperformanceperformance-analysisperformance-metricsperformance-monitoringperformance-tuningperformance-visualizationprofilerprofiling
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/myperf4j)Questions
- Does MyPerf4J run?
- MyPerf4J runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 16 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test MyPerf4J?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 984684270482. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test MyPerf4J?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does MyPerf4J take to install?
- 16 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does MyPerf4J need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing MyPerf4J?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does MyPerf4J compare with the alternatives?
- Of the 138 agent projects Argusic has installed and timed, MyPerf4J was the 108th fastest to reach a running state, and 92 of 138 reached one at all.
- Where is the evidence for MyPerf4J?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.