No filters applied - covering 100% of reports
CPU
Note: Java does not provide much info about the CPU
Available processors
Values returned by Runtime.getRuntime().availableProcessors()
| Processor count | Reports | Share | Cumulative |
|---|---|---|---|
| 64 | 6 | 0.00% |
0.00% |
| 48 | 4 | 0.00% |
0.01% |
| 40 | 3 | 0.00% |
0.01% |
| 36 | 8 | 0.01% |
0.02% |
| 32 | 165 | 0.12% |
0.14% |
| 28 | 9 | 0.01% |
0.14% |
| 24 | 622 | 0.46% |
0.60% |
| 20 | 806 | 0.59% |
1.19% |
| 16 | 4,915 | 3.60% |
4.79% |
| 14 | 1 | 0.00% |
4.79% |
| 12 | 6,945 | 5.09% |
9.89% |
| 11 | 2 | 0.00% |
9.89% |
| 10 | 49 | 0.04% |
9.92% |
| 9 | 1 | 0.00% |
9.92% |
| 8 | 96,448 | 70.72% |
80.64% |
| 7 | 6 | 0.00% |
80.65% |
| 6 | 11,821 | 8.67% |
89.31% |
| 4 | 11,667 | 8.55% |
97.87% |
| 3 | 228 | 0.17% |
98.04% |
| 2 | 2,670 | 1.96% |
99.99% |
| 1 | 9 | 0.01% |
100.00% |
Binary tree benchmark
Using this code from the Benchmarks Game. Benchmark has been run for 6, 8 and 10 nodes sequentially per iteration, 20 iterations in total, with 1.5s warmup.
Every value listed here is a duration in microseconds, smaller is faster.
Note: this is not a proper benchmark and it only shows some rough numbers to see how different platforms act in the same conditions. A complete benchmark would take much more time and I did not want to make players wait for too long or to drain their battery.
| Min | Avg | Max |
|---|---|---|
| 963 | 12,462 | 11,981,368 |