Number of reports matching the filters
Matching | Total | Match % | |
---|---|---|---|
All reports | 29,799 | 136,385 | 21.85% |
Android | 0 | 94,055 | 0.00% |
Desktop | 29,799 | 29,799 | 100.00% |
iOS | 0 | 12,531 | 0.00% |
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.02% |
0.02% |
48 | 4 | 0.01% |
0.03% |
40 | 3 | 0.01% |
0.04% |
36 | 8 | 0.03% |
0.07% |
32 | 165 | 0.55% |
0.62% |
28 | 9 | 0.03% |
0.65% |
24 | 620 | 2.08% |
2.73% |
20 | 806 | 2.70% |
5.44% |
16 | 4,915 | 16.49% |
21.93% |
14 | 1 | 0.00% |
21.94% |
12 | 6,941 | 23.29% |
45.23% |
11 | 2 | 0.01% |
45.24% |
10 | 7 | 0.02% |
45.26% |
9 | 1 | 0.00% |
45.26% |
8 | 7,309 | 24.53% |
69.79% |
7 | 4 | 0.01% |
69.80% |
6 | 1,661 | 5.57% |
75.38% |
4 | 6,352 | 21.32% |
96.69% |
3 | 26 | 0.09% |
96.78% |
2 | 955 | 3.20% |
99.99% |
1 | 4 | 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 | 3,773 | 11,981,368 |