Skip to content
Better HN
Top
Best
Ask
Show
New
Jobs
Search
⌘K
0 points
monocasa
6y ago
0 comments
Save
Share
Yeah, they already weren't allocating, it was a GC pause that just scanned and would come up with essentially no extra garbage every two minutes.
0 comments
1 comments · 1 top-level
top
newest
oldest
azakai
6y ago
A pool allocator could have reduced the number of existing allocations (1 big one instead of many small ones), making those spikes less significant. (But that depends on how Go handles interior pointers and GC, so I'm not sure.)
2 more replies
j
/
k
navigate · click thread line to collapse