Github user leventov commented on the issue:
https://github.com/apache/logging-log4j2/pull/87
New latency benchmarking results "done right" (with Pacer), On 4-core MBP
with SSD, benchmarking with 3 threads:
- [200
messages/sec/thread](https://cdn.rawgit.com/leventov/eee84006a53dfb8d2acaebfe126bb499/raw/805c548d1f41e49e67b6815dde84d92be0568012/load200.html)
- [2k
messages/sec/thread](https://cdn.rawgit.com/leventov/eee84006a53dfb8d2acaebfe126bb499/raw/805c548d1f41e49e67b6815dde84d92be0568012/load2k.html)
- [20k
messages/sec/thread](https://cdn.rawgit.com/leventov/eee84006a53dfb8d2acaebfe126bb499/raw/805c548d1f41e49e67b6815dde84d92be0568012/load20k.html)
- [100k
messages/sec/thread](https://cdn.rawgit.com/leventov/eee84006a53dfb8d2acaebfe126bb499/raw/805c548d1f41e49e67b6815dde84d92be0568012/load100k.html)
I still use JMH to piggy-back threading, warmup, setup/teardown, parameter
setting, etc.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
