diff options
| -rw-r--r-- | doc/mimalloc-doc.h | 2 | ||||
| -rw-r--r-- | readme.md | 12 |
2 files changed, 7 insertions, 7 deletions
diff --git a/doc/mimalloc-doc.h b/doc/mimalloc-doc.h index 7c238d2..5911340 100644 --- a/doc/mimalloc-doc.h +++ b/doc/mimalloc-doc.h @@ -1209,7 +1209,7 @@ synthetic benchmarks that see how the allocator behaves under more extreme circumstances. In our benchmarks, _mimalloc_ always outperforms all other leading -allocators (_jemalloc_, _tcmalloc_, _Hoard_, etc) (Apr 2019), +allocators (_jemalloc_, _tcmalloc_, _Hoard_, etc) (Jan 2021), and usually uses less memory (up to 25% more in the worst case). A nice property is that it does *consistently* well over the wide range of benchmarks. @@ -458,8 +458,8 @@ the memory compacting [_Mesh_](https://github.com/plasma-umass/Mesh) (git:51222e Bobby Powers _et al_ \[8], and finally the default system allocator (glibc, 2.27) (based on _PtMalloc2_). -<img width="90%" src="doc/bench-c5-18xlarge-2020-01-20-a.svg"/> -<img width="90%" src="doc/bench-c5-18xlarge-2020-01-20-b.svg"/> +<img width="90%" src="doc/bench-2020/bench-c5-18xlarge-2020-01-20-a.svg"/> +<img width="90%" src="doc/bench-2020/bench-c5-18xlarge-2020-01-20-b.svg"/> Any benchmarks ending in `N` run on all processors in parallel. Results are averaged over 10 runs and reported relative @@ -550,8 +550,8 @@ having a 48 processor AMD Epyc 7000 at 2.5GHz with 384GiB of memory. The results are similar to the Intel results but it is interesting to see the differences in the _larsonN_, _mstressN_, and _xmalloc-testN_ benchmarks. -<img width="90%" src="doc/bench-r5a-12xlarge-2020-01-16-a.svg"/> -<img width="90%" src="doc/bench-r5a-12xlarge-2020-01-16-b.svg"/> +<img width="90%" src="doc/bench-2020/bench-r5a-12xlarge-2020-01-16-a.svg"/> +<img width="90%" src="doc/bench-2020/bench-r5a-12xlarge-2020-01-16-b.svg"/> ## Peak Working Set @@ -559,8 +559,8 @@ see the differences in the _larsonN_, _mstressN_, and _xmalloc-testN_ benchmarks The following figure shows the peak working set (rss) of the allocators on the benchmarks (on the c5.18xlarge instance). -<img width="90%" src="doc/bench-c5-18xlarge-2020-01-20-rss-a.svg"/> -<img width="90%" src="doc/bench-c5-18xlarge-2020-01-20-rss-b.svg"/> +<img width="90%" src="doc/bench-2020/bench-c5-18xlarge-2020-01-20-rss-a.svg"/> +<img width="90%" src="doc/bench-2020/bench-c5-18xlarge-2020-01-20-rss-b.svg"/> Note that the _xmalloc-testN_ memory usage should be disregarded as it allocates more the faster the program runs. Similarly, memory usage of |