You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But, I think you have them beat on performance for suitable applications. 😄
In fact, the performance is mind blowing! Wow! (I ran your benchmarks, and read through them)
I honestly wouldn't have thought of starting with sync.Pool, although I did look at it recently and noticed
it was heavily optimized.
I guess the main advantage of starting with sync.Pool over using a regular lock-free ring-buffer is
the flexibility to have some dynamic growth of the buffer size??
Is that why you started with sync.Pool?
I'd love to hear more about your thought process, it's very intriguing, and congrats on a nice piece of work.
Oh! also curious if you are using this in a production use-case... ?
Cameron/Seattle
The text was updated successfully, but these errors were encountered:
Hi Marcelo, I was lucky to find your project when exploring SPMC projects.
Any chance you would add a license file? I see you added MIT on your other projects, that would be nice if you can use that here too.
Anyway, aside from the license, this is super super interesting to me!
I'm also aware of this: https://github.com/Workiva/go-datastructures#queue
But, I think you have them beat on performance for suitable applications. 😄
In fact, the performance is mind blowing! Wow! (I ran your benchmarks, and read through them)
I honestly wouldn't have thought of starting with sync.Pool, although I did look at it recently and noticed
it was heavily optimized.
I guess the main advantage of starting with sync.Pool over using a regular lock-free ring-buffer is
the flexibility to have some dynamic growth of the buffer size??
Is that why you started with sync.Pool?
I'd love to hear more about your thought process, it's very intriguing, and congrats on a nice piece of work.
Oh! also curious if you are using this in a production use-case... ?
Cameron/Seattle
The text was updated successfully, but these errors were encountered: