kiper220/mimalloc
1
0
Fork 0
mirror of https://github.com/microsoft/mimalloc.git synced 2025-08-23 15:54:47 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions

update benchmark references

Browse source
This commit is contained in:
Daan Leijen 2021-01-31 10:23:57 -08:00
parent 58678ac4eb
commit 558c8d085e
2 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/mimalloc-doc.h
View file

@ -1209,7 +1209,7 @@ synthetic benchmarks that see how the allocator behaves under more
extreme circumstances. extreme circumstances.
In our benchmarks, _mimalloc_ always outperforms all other leading 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). 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 A nice property is that it does *consistently* well over the wide
range of benchmarks. range of benchmarks.

12
readme.md
View file

@ -458,8 +458,8 @@ the memory compacting [_Mesh_](https://github.com/plasma-umass/Mesh) (git:51222e
Bobby Powers _et al_ \[8], Bobby Powers _et al_ \[8],
and finally the default system allocator (glibc, 2.27) (based on _PtMalloc2_). 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-2020/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-b.svg"/>
Any benchmarks ending in `N` run on all processors in parallel. Any benchmarks ending in `N` run on all processors in parallel.
Results are averaged over 10 runs and reported relative 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 The results are similar to the Intel results but it is interesting to
see the differences in the _larsonN_, _mstressN_, and _xmalloc-testN_ benchmarks. 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-2020/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-b.svg"/>
## Peak Working Set ## 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 The following figure shows the peak working set (rss) of the allocators
on the benchmarks (on the c5.18xlarge instance). 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-2020/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-b.svg"/>
Note that the _xmalloc-testN_ memory usage should be disregarded as it Note that the _xmalloc-testN_ memory usage should be disregarded as it
allocates more the faster the program runs. Similarly, memory usage of allocates more the faster the program runs. Similarly, memory usage of