Re: [go-nuts] Sync pool old data

2017-10-12 Thread 'Bryan Mills' via golang-nuts
On Wednesday, October 11, 2017 at 4:03:30 PM UTC-4, Ian Lance Taylor wrote: > > if the number of parallel operations does not vary > significantly, a freelist is a simpler and more effective technique. > A freelist might be simpler, but it isn't necessarily more effective. sync.Pool combines tw

Re: [go-nuts] Sync pool old data

2017-10-11 Thread Ian Lance Taylor
On Wed, Oct 11, 2017 at 12:50 PM, XXX ZZZ wrote: > > So I'm starting to play with sync pool on a program that needs to allocate a > ton of short lived objects per server request. Performance seems to be > better when using sync pool however I've noticed that upon releasing the > object and then re

[go-nuts] Sync pool old data

2017-10-11 Thread XXX ZZZ
Hello, So I'm starting to play with sync pool on a program that needs to allocate a ton of short lived objects per server request. Performance seems to be better when using sync pool however I've noticed that upon releasing the object and then retrieving it again, will produce a "new object" wi