Anish Mukherjee

@jdvjdv82 no issues, thanks a lot for your help :) We can observe that ubuntu performance has improved considerably since last run but its still slow for SPSC mode for...

@jdvjdv82 its because ZenQ uses sync.Pool internally if pool objects get allocated more in the first phase, then the first halves will be slower due to heavy allocation and the...

I have already opened an issue for it https://github.com/golang/go/issues/52652

We can gain even further optimizations by using runtime internal methods like gopark instead of spinning mechanism which is the current implementation thereby ensuring minimum required goroutine utilization without any...

@welldonexing thanks for the update, xxh3 is indeed faster and I am also planning to make a switch on another note how does your xxh3 library compare with [Cyan4973/xxHash](https://github.com/Cyan4973/xxHash) performance...

nice, I will change to xxh3 hashing and publish a new release possibly this weekend PS:- I think xxh3 will give a considerable speed boost for long string key types...

@mvestnik can you run a benchmark test with the FNV hash algorithm similar to this one https://github.com/alphadose/haxmap/blob/main/benchmarks/map_test.go ? You can use `haxmap.SetHasher()` function to override the default xxhash algo with...

I will check this out and get back to you

@chenfeisoft this is by design. The goroutine calling `Read()` polls continuously (CPU spin wait) to check if data is available or not. The queue is optimized for lowest possible latency.

@anthdm I am running the go 1.19.0 darwin/arm64, I cloned the latest main branch and for me `go run examples/simple/main.go` seems to be working I have never encountered that error...