Jakub Wosyka

``` $ go test -bench=. -benchmem benchmarks/simple/*.go goos: windows goarch: amd64 cpu: AMD Ryzen Threadripper 3960X 24-Core Processor Benchmark_Chan_NumWriters1_InputSize600-48 31578 35531 ns/op 0 B/op 0 allocs/op Benchmark_ZenQ_NumWriters1_InputSize600-48 32344 35370 ns/op...

+ again 48 cpu in ms windows in GIT shell ``` $ go run benchmarks/simple/main.go With Input Batch Size: 60 and Num Concurrent Writers: 1 Native Channel Runner completed transfer...

yep, just let me know here. I will test on both platforms and different PCs again. I did not finish also on laptop 8 core i7.

Hello @alphadose, cpu: AMD Ryzen Threadripper 3960X 24-Core Processor 128 GB RAM, many NVME pcie 4.0 SSDs following test is on ms windows 11 ``` $ go run benchmarks/selector/main.go With...

ubuntu ``` go run benchmarks/selector/main.go With Input Batch Size: 60 and Num Concurrent Writers: 4 Chan Select Runner completed transfer in: 43.181µs ZenQ Select Runner completed transfer in: 180.5µs ====================================================================...

go job!!! memory allocation is much better and that matters a lot

hi, just think about how you doing ;-) ``` $ go test -bench=. -benchmem benchmarks/simple/*.go goos: windows goarch: amd64 cpu: AMD Ryzen Threadripper 3960X 24-Core Processor Benchmark_Chan_NumWriters1_InputSize600-48 35980 33519 ns/op...

ubuntu ``` go test -bench=. -benchmem benchmarks/simple/*.go goos: linux goarch: amd64 cpu: AMD Ryzen Threadripper 3960X 24-Core Processor Benchmark_Chan_NumWriters1_InputSize600-48 29367 63828 ns/op 0 B/op 0 allocs/op Benchmark_ZenQ_NumWriters1_InputSize600-48 26434 42871 ns/op...

@alphadose sorry for delay, here are the benchmarks for both systems

any idea why those measurements are so inconsistent? ``` jdvvo@AMD-TRX MINGW64 ~/GolandProjects/zenq (main) $ go test -bench=. -benchmem benchmarks/simple/*.go goos: windows goarch: amd64 cpu: AMD Ryzen Threadripper 3960X 24-Core Processor...