[go-nuts] Re: Performance of unique package

2024-06-26 Thread Juliusz Chroboczek
After fixing the bugs pointed out by Michael (I'm incompetent), here are the new results: Uninterned-8120ms ą18% Map-8 140ms ą 2% LockedMap-8 139ms ą 2% LockedParellel-8146ms ą 2% SyncMap-8 253ms ą 4% SyncMapParallel-8 109ms ą 9

[go-nuts] Re: Performance of unique package

2024-06-26 Thread Juliusz Chroboczek
> In terms of lookup/insertion/etc., I would expect unique.Make to perform > much better than a locked map when doing operations in parallel, but > perform slightly worse when everything is done on a single core. It looks like your intuition was correct. Sync.Map still performs better, though.

[go-nuts] Re: Performance of unique package

2024-06-26 Thread Juliusz Chroboczek
> In terms of lookup/insertion/etc., I would expect unique.Make to perform > much better than a locked map when doing operations in parallel, but > perform slightly worse when everything is done on a single core. Thanks, that's encouraging. I'll see if I can conjure a realistic benchmark. -- Yo

[go-nuts] Re: Performance of unique package

2024-06-25 Thread 'Michael Knyszek' via golang-nuts
The unique package itself has a few benchmarks you can run if you'd like, though they're somewhat limited. They exist primarily to validate that the implementation has