Nov 2, 2025

Thinking about json, that's a different problem, since boost::json operates over an object model. However the boost::json::value (intermediate json DOM) could be populated directly from store queries as well. In other words, have the query produce the model instance - instead of having the boost::json value convertor produce it from the annotated object model. This again would cut out the normal form queries. Those are really only necessary for validation. That's probably 2 days of work in the store - first day to figure out the proper boost::json pattern. That would cut way down on memory allocations and probably cut the json output time in half (presently 75ms for large blocks on my machine, vs. 40ms for hex, and 35ms for wire encoding). So maybe json in 40ms, hex in 20ms, and 18ms for wire. Cut that in half for a 2x faster CPU, as I'm running 2.1GHz threads and these are entirely CPU-bound single threaded operations.