Use orjson or ujson instead of build-in json

[tyzhnenko]

I've done some benchmarks based on py-frameworks-bench approach. Not a big deal but the test has a small simple JSON sample. For bigger nested objects results should be more enjoyable.

# local build blacksheep 2.0a5 with build-in json
Running 15s test @ http://localhost:8080/api/users/1/records/1?query=test
  4 threads and 64 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.25ms  117.80us   6.07ms   86.48%
    Req/Sec     7.14k   198.95     7.42k    71.85%
  428989 requests in 15.10s, 83.87MB read
Requests/sec:  28404.70
Transfer/sec:      5.55MB

# local build blacksheep 2.0a5 with orjson
Running 15s test @ http://localhost:8080/api/users/1/records/1?query=test
  4 threads and 64 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.19ms   88.91us   4.76ms   85.71%
    Req/Sec     7.33k   151.58     7.57k    85.26%
  440445 requests in 15.10s, 86.11MB read
Requests/sec:  29166.52
Transfer/sec:      5.70MB

# local build blacksheep 2.0a5 with ujson
Running 15s test @ http://localhost:8080/api/users/1/records/1?query=test
  4 threads and 64 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     2.19ms  102.59us   7.65ms   91.17%
    Req/Sec     7.34k   160.96     7.58k    89.90%
  441368 requests in 15.10s, 86.29MB read
Requests/sec:  29227.64
Transfer/sec:      5.71MB

[RobertoPrevato]

Hi @tyzhnenko
Thank you for these benchmarks. BlackSheep already supports an easy way to configure the library used for JSON:

https://www.neoteroi.dev/blacksheep/settings/#example-using-orjson

I prefer to keep using the built-in json package as default, to not add an extra dependency. The important thing is that users can easily adopt alternative libraries if they wish so.