@Ken how much latency can you shave off with shared memory vs unix sockets? Cc @Justin if you have any comparisons?
Thanks! On Wednesday, January 23, 2019 at 1:19:13 PM UTC-8 [email protected] wrote: > I think the way I'd do shared memory Cap'n Proto would be to have a large > shared memory space mapped upfront, allocate/write each message within the > space, and then signal to the other process "you can find a new message > located at position X", "I am done with the message located at position Y", > etc. > > This has always been something I intended to implement, but so far it > hasn't come up as a priority. Sending messages over a unix socket is easy > and works well, so I'd recommend trying that first, and considering shared > memory transport as a possible optimization later on. > > -Kenton > > On Sun, Jan 20, 2019 at 11:23 PM Omega Ishendra <[email protected]> > wrote: > >> Hi all, >> >> I know that communication between two processes can be done mainly using >> two methods. >> >> 1. Shared Memory >> 2. Message passing >> >> >> my initial idea about capnp is, it is using "Message Passing". >> >> Is my idea correct? >> Can we do Inter-Process-Communication using shared memory in capnp? >> which is the faster? >> >> Thanks, >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Cap'n Proto" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> Visit this group at https://groups.google.com/group/capnproto. >> > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/7c4811b6-1468-419a-81e4-4610cd818818n%40googlegroups.com.
