Good point, thank you Bryan.
Also note that assigning a func value to p.New seems standard for the use case
"if nil, then create one" (I don't know the perf implications).
Cheers
Val
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscri
On Friday, October 6, 2017 at 5:32:06 PM UTC-4, Ian Lance Taylor wrote:
>
> On Fri, Oct 6, 2017 at 1:23 PM, XXX ZZZ >
> wrote:
> >
> > So we are making a platform where we have to use a TON of short lived
> > structs, in order to optimize this we intend to use sync pool, however
> on
> > our
On Fri, Oct 6, 2017 at 1:23 PM, XXX ZZZ wrote:
>
> So we are making a platform where we have to use a TON of short lived
> structs, in order to optimize this we intend to use sync pool, however on
> our benchmark tests I have found that it only seems to improve performance
> when the struct is big
Hello,
So we are making a platform where we have to use a TON of short lived
structs, in order to optimize this we intend to use sync pool, however on
our benchmark tests I have found that it only seems to improve performance
when the struct is big enough, for smaller structs ie: (4-5 string va
