Hi, Maybe this is an easy question, maybe it's not. I guess we're about to find out together. I'm working on application that I need to be able to handle large amounts of requests in parallel. It needs to be fast in user time, not CPU time. If I hit this with as many requests per second as it can take, it begins to get bottlenecked by single-threaded performance.
My question is: is there space in the capnproto protocol to have multithreaded receivers, or have the scheduling use multiple threads for its event queue? I've seen it talked about, but unfortunately, I've not found any documentation regarding it. I've been using go-capnproto2 for all of this, but my reading has suggested I'm plainly missing something. On another side, mentally at least, I'd imagine that it would be nice to allocate a number of worker threads to handle queueing, but that may be a fight (against myself) for another day. Or, allowing me to allocate tasks to another thread. Thanks in advance! And sorry for the kinda dumb question. --Eamonn -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/4405b081-d9d7-49aa-a128-d0c168daf4fc%40googlegroups.com.
