Re:Proposed New Go GC: Transaction-Oriented Collector
by sebcat on Friday June 24, 2016 @02:23PM
(#11972170)
> I don't have high hopes for this algorithm, because my intuition is that transactions aren't common enough to make a big difference.
Every served request by net/http#Server, net/rpc#Server and similar gets its own goroutine. That is to say, its own transaction. Memory allocated within that transaction will be associated with it. Should make a positive difference for server software.
Every served request by net/http#Server, net/rpc#Server and similar gets its own goroutine. That is to say, its own transaction. Memory allocated within that transaction will be associated with it. Should make a positive difference for server software.