3 ms·
sure it is. however isn't most xml or json marshalled communication I/O bound? so even though it could be faster it also is "fast enough"?
by froh 5y ago
sure it is. however isn't most xml or json marshalled communication I/O bound? so even though it could be faster it also is "fast enough"?
- masklinn 5y agoIt depends a lot how you're getting it and what you're doing with it. The existence of projects like rapidjson, simdjson, … indicates that even without GTAV-style mistakes, JSON enc/dec can absolutely be your limiting factor. Even more so if you're on a local network (e.g. between machines in the same DC) where bandwidth is… essentally infinite, for all intents and purposes? When you've got 10Gb/s or even 100Gb/s between your racks, odds are IO is only the limiting factor for very short messages (lots of framing overhead). As for XML, it's an absolute bear to encode and decode, documents are often large (dozens, hundreds, even thousands of GB), and the format is complicated enough that writing truly fast parsers is difficult. Being CPU-bound when XML is involved is routine, especially if you need a DOM.