2 ms·
> wouldn't the majority of allocations still happen during a request? Could you please clarify this question? Do you mean that if cached objects are a small pa
by unlogic 7y ago
> wouldn't the majority of allocations still happen during a request?
Could you please clarify this question? Do you mean that if cached objects are a small part of the total allocation rate, then generation GCs work well with that?
- jashmatthews 7y agoExactly. Go explored a request oriented collector with explicit generational boundaries.
- unlogic 7y agoWell, if caching takes a small part of the overall workload, then you can't really say it's a "cache workload" or "cache-heavy workload", right? My answer meant that Shenandoah would work well in a program where cache occupies like 70-80% of the heap, and generational GCs might not. But surely, neither are going to break from a 1%-heap cache.