Skip to content

Hopefully fix table formatting #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nekevss merged 1 commit into from
Mar 6, 2026
Merged

Hopefully fix table formatting #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions notes/coll_alloc_supertrait/arena2_vs_arena3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ but arena3 fits more objects into the same amount of memory
arena2 is faster at every size and the gap grows as object count goes up

| objects | arena3 | arena2 |
|---------|---------|---------|
| 100 | 1.02 µs | 643 ns |
| 500 | 4.15 µs | 1.83 µs |
| 1000 | 8.36 µs | 2.77 µs |
Expand All @@ -33,6 +34,7 @@ header on every object. But this bench is measuring allocation time, not memory
writing the header is cheap, what costs time in arena3 is the size class routing.

| objects | arena3 (0-byte header) | arena2 (8-byte header) |
|---------|---------|---------|
| 100 | 781 ns | 257 ns |
| 500 | 3.56 µs | 1.08 µs |
| 1000 | 7.02 µs | 2.15 µs |
Expand Down Expand Up @@ -89,6 +91,7 @@ the whole suite
time to free all objects and reclaim dead arenas:

| objects | arena3 | arena2 |
|---------|---------|---------|
| 100 | 951 ns | 665 ns |
| 500 | 2.57 µs | 2.11 µs |
| 1000 | 4.65 µs | 4.97 µs |
Expand Down