You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Chronicle Logger consumes 100% CPU (all 40 vCPUs are busy, synchronization is done with [CAS](https://en.wikipedia.org/wiki/Compare-and-swap)) while Log4JLoggerBenchmark only consumes 15% CPU.
124
+
125
+
### Heap allocation
126
+
127
+
The Chronicle Logger allocates around 0.65 GB of [heap](https://www.baeldung.com/java-stack-heap) when the benchmark is executed. Log4J needs much more memory and allocated over 3 GB in the benchmark.
The Chronicle Logger consumes 100% CPU (all 40 vCPUs are busy, synchronization is done with [CAS](https://en.wikipedia.org/wiki/Compare-and-swap)) while Log4JLoggerBenchmark only consumes 15% CPU.
172
-
173
-
### Heap allocation
174
-
175
-
The Chronicle Logger allocates around 0.65 GB of [heap](https://www.baeldung.com/java-stack-heap) when the benchmark is executed. Log4J needs much more memory and allocated over 3 GB in the benchmark.
54
+
Since the project evolved over time, the results are not always comparable.
55
+
The [benchmark archive](BENCHMARK_HISTORY.MD) contains the results of benchmarks of all previous version of the repository.
56
+
57
+
### Logger initialization
58
+
59
+
Since `v0.2.0` the repo contains benchmarks that check the initialization time of the logger.
60
+
All loggers are initialized really fast (about 40,000,000 calls per second on my machine) and the performance is independent of the logger configuration.
176
61
177
62
## Kudos
178
63
179
-
[Oleg Mazurov](https://github.com/OlegMazurov) helped me by executing the tests on a powerfull linux server.
64
+
The following people helped to improve the benchmark:
65
+
66
+
-[Oleg Mazurov](https://github.com/OlegMazurov) helped me by executing the tests on a powerfull linux server.
67
+
-[Peter Lawrey](https://github.com/peter-lawrey) helped me to improve the chronicle benchmarks.
0 commit comments