mirror of
https://github.com/bspeice/speice.io
synced 2024-12-22 08:38:09 -05:00
Fix link
This commit is contained in:
parent
6dcbc1a72c
commit
3bd6550c34
@ -135,7 +135,7 @@ principle is the same: running the allocator to allocate/deallocate memory takes
|
|||||||
be put to better use. Understanding when your language interacts with the allocator is crucial, and
|
be put to better use. Understanding when your language interacts with the allocator is crucial, and
|
||||||
not always obvious. For example: C++ and Rust don't allocate heap memory for iterators, but Java
|
not always obvious. For example: C++ and Rust don't allocate heap memory for iterators, but Java
|
||||||
does (meaning potential GC pauses). Take time to understand heap behavior (I made a
|
does (meaning potential GC pauses). Take time to understand heap behavior (I made a
|
||||||
[a guide for Rust](/2019/02/understanding-allocations-in-rust.html)), and look into alternative
|
[a guide for Rust](/2019/02/understanding-allocations-in-rust)), and look into alternative
|
||||||
allocators ([jemalloc](http://jemalloc.net/),
|
allocators ([jemalloc](http://jemalloc.net/),
|
||||||
[tcmalloc](https://gperftools.github.io/gperftools/tcmalloc.html)) that might run faster than the
|
[tcmalloc](https://gperftools.github.io/gperftools/tcmalloc.html)) that might run faster than the
|
||||||
operating system default.
|
operating system default.
|
||||||
|
Loading…
Reference in New Issue
Block a user