Use orjson to improve JSON marshalling performance

[amotl]

About

Using orjson for JSON marshalling can yield performance wins. It has been used in CrateDB Toolkit already, in that case its sister library orjsonl. Thanks, @widmogrod.

References

• json.dumps takes significant CPU time in data heavy workloads like ETL or streaming #689
• Table Loader and MongoDB: A few refinements cratedb-toolkit#270

Downstream

• Update to crate-2.0.0, which uses orjson for JSON marshalling crash#459
• Update to crate-2.0.0, which uses orjson for JSON marshalling cratedb-toolkit#349
• Update to crate-2.0.0, which uses orjson for JSON marshalling cratedb-examples#811
• Update to crate-2.0.0, which uses orjson for JSON marshalling sqlalchemy-cratedb#195
• Update to crate-2.0.0, which uses orjson for JSON marshalling langchain-cratedb#23
• Update to crate-2.0.0, which uses orjson for JSON marshalling academy-fundamentals-course#49
• https://github.com/crate/cloud-api/pull/3038
• https://github.com/crate/stevedore/pull/325
• https://github.com/crate/grand-central/pull/189

[amotl]

Hi again. Thanks for the quick review. I've just added a few thoughts about the consequences of removing the traditional CrateJsonEncoder.

[kneth]

Great to see this performance fix. Thanks to @amotl and @seut!

[seut]

looks good

[surister]

Do we have a benchmark?

[amotl]

Do we have a benchmark?

It's not a benchmark, but @widmogrod shared a flamegraph before/after over at #689 (comment).