zero-copy about node-nanomsg HOT 4 CLOSED

btw outlook is super busy this week for me.

i think i could reasonably PR this feature next week, so if anyone wants to take a stab at it in the meantime, then by all means, would be happy to review or build on that PR!

from node-nanomsg.

this morning i was reading from The Art of Unix Programming and some lines stuck me from the section on Compactness and the Strong Single Center:

[Compactness] is an often-overlooked strength of the Unix tradition. Many of its most effective tools are thin wrappers around a direct translation of some single powerful algorithm.

-Eric S. Raymond

IMO, that's exactly what we're trying to do here in the src/node_nanomsg.cc file.

from node-nanomsg.

@nickdesaulniers and i discussed this last night and we are going to take our time here basically.

One thing we talked about on zero-copy is, first of all, it's kind of complicated to get right and for some common architectures this will have little to no impact.

We are in no rush to implement this; however once we do, look out for a win in application performance probably mostly for off-cloud networked linux machines. Like dedicated servers or data centers with bare metal direct access to instruction sets/caches soldered in proximity to the system's core processor chips

@sustrik has mentioned before:

that API is designed in such a way that it allows CPU-bypass in RDMA and other such super-efficient technologies

from node-nanomsg.

we tried this and it didn't really work.

from node-nanomsg.