On 5/13/25 9:17 PM, Dmitry Porokh via dev wrote: > Introduce two implementations of the jsonrpc > input parsing. One "normal" that works as before > on the receiver thread. And "threaded" that > runs additional thread per each rpc session. > > In "threaded" case all received data is sent to > separate thread to be parsed and result is received > on receiver thread as parsed jsons. > > Motivation for "threaded" version is to free up > resources of receiver thread for other processing > work. Specifically in ovn / northd json parsing can > take from 9% to 30% of all computations. > > Signed-off-by: Dmitry Porokh <dpor...@nvidia.com> > ---
Hi, Dmitry. nit: This patch should have an "RFC" in the subject prefix, not "PATCH". While I agree that input json parsing does have impact on performance, it feels like there are still many other things that can be optimized in memory management and the processing logic before we try to throw more cores on the problem. We're trying not to introduce multi-threading unless there is absolutely no other way to improve performance in a particular place and there is an actual real-world use case where it is necessary. This doesn't seem to match the description of the situation with the jsonrpc input processing at this time. Multi-threading brings a lot of complexity and complicates the logic, which in most cases isn't worth to trade off. Best regards, Ilya Maximets. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
