On 4/13/23 13:35, Roberto Bartzen Acosta wrote:
> Hey folks,
> 
> I've been reading some docs about parser acceleration for json and I thought 
> of the ovsdb case. I already had serious performance issues with ovsdb in 
> large-scale deployments. I noticed was that most of the processing was 
> related to ovsdb tasks.
> 
> Do you have any idea if any acceleration routine using vectorized 
> classification concepts/SIMD as presented in this article [1]/project[2] 
> would be applicable to the case of JSON RPC parsers?
> 
> Maybe Ilya, who knows more deeply about ovsdb approach and who evaluates 
> performance using the ovn-heater can contribute here.
> 
> [1] - https://arxiv.org/abs/1902.08318 <https://arxiv.org/abs/1902.08318>
> [2] - https://github.com/simdjson/simdjson 
> <https://github.com/simdjson/simdjson>
> 
> Kind regards,
> Roberto

Hi.  Thanks for interesting links!

It might certainly be possible to improve the performance of a JSON
parser with more compiler hacks and SIMD instructions.  However, in
my experience, the parser itself doesn't really show up in testing
as a big performance bottleneck.  Especially after some good changes
made last year by Rosemarie:
  
https://github.com/openvswitch/ovs/commit/2f16123c1bf0793381683ede3d63ae6da379d9b7
So, making it faster may not worth the cost of increased code complexity.

The main challenges in ovsdb-server these days are mostly related to
filtering large amounts of data and sending it out, not really the
JSON parsing, AFAIK.

Best regards, Ilya Maximets.
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to