kvuj/allocPool
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README: Fix typo.

Browse Source
This commit is contained in:
Timothée Leclaire-Fournier 2024-03-12 15:06:26 -04:00
parent fd8203400c
commit a86dea3901
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -12,9 +12,9 @@ We avoid false sharing by keeping a high amount of work per thread. This should
lead to cache lines not being shared between threads. In the advent that cache lead to cache lines not being shared between threads. In the advent that cache
lines would overlap, we use a smaller amount of threads with a bit more work lines would overlap, we use a smaller amount of threads with a bit more work
per thread. This option is enabled with the `bool enableFalseSharingMitigations` per thread. This option is enabled with the `bool enableFalseSharingMitigations`
parameter in the constructor. It is on by default and can be disabled in the advent parameter in the constructor. It is on by default and can be disabled in case
that you very big objects where writing pointers in the `std::vector` will not be the that you have big objects where writing pointers in the `std::vector` will
bottleneck. not be the bottleneck and where more threads will benefit the performance.
While this pool uses a hashmap and a pivot to make `returnPtr(ptr)` extremely fast, While this pool uses a hashmap and a pivot to make `returnPtr(ptr)` extremely fast,
when saving the pointers, the main bottleneck is in the locking and unlocking of the when saving the pointers, the main bottleneck is in the locking and unlocking of the