Axel Rietschin

The current naming makes zero sense. Where is the 32 vs. 64 bit flag? ARM vs Intel? MSVC vs Intel C++? There should be two flavors: libzmq.dll and libzmqd.dll, where...

Yes it looks like both refer to the same thing. I’ll have a look at the PR. I think it’s possible to fix the issue without breaking existing client code....

Fascinating. I’d do a couple of lines of inline asm, or use intrinsics and plain C and be sure. I know intrinsics aren’t very portable but that’s one of those...

Not sure this is still current but you should consider building the library with symbols so the stack trace makes sense.

I've looked at this as I, too, believe it's worth doing something as in some scenario (inproc and presumably with other very fast transports) the dominant location where time is...

@f18m Yep you can check my fork of the project. It’s a bit of a battlefield atm, but it builds on Windows, all tests pass, and it’s a drop-in binary...

Benefits of a custom allocator for inproc workloads. Here I'm using Intel's Scalable Allocator, part of Intel oneAPI / Threading Building Blocks. There is definitely an advantage. One thing jumps...

I went ahead in my fork and was able to increase the vsm to 40 bytes (up from 33) by repacking the group_t and msg_t structs and reducing the short...

What needs to be counted are the calls to manage_random. I did it in my fork like this: https://github.com/axelriet/libzmq/commit/2700a87adf227ec9d54720fa9caa22f76692a752

Two separate things: 1) It should not crash (there is a bug) 2) If you are using pub-sub over TCP that is not the best way to multicast a file...