Krzysztof Ciesielski

Thanks for the insights, @plokhotnyuk. As Adam suspected, I wasn't aware of the nuances you mentioned. Looks like building all of our desired features on top of jsoniter-scala requires a...

@adamw As we discussed today, we'd like to work some more on Tapir performance tests. Before specifying concrete scenarios that are important in the first place, let's make sure we...

1. Good point, the way we're going to test Tapir is specific. For most cases we are aiming to compare latencies between backends, and we can easily achieve a reference...

@adamw A proposition of scenarios/backends to start with: **Simple GET latency** Current test Concurrent users calling dummy GET endpoints. Rationale: A simple test which allows to quickly check overhead on...

> Simple GET latency -> this would also involve comparing to no-tapir setups? http4s and pekko are easy, netty - probably not so much? Yes, the no-tapir setups are in...

> Maybe pekko-http will provide a good enought baseline? As a server, it's rather fast :) Otherwise, we might look at vertx - it's one of the fastest servers out...

Let's see, we could achieve this by parameterizing scnearios with concurrent user count. Run with `nUsers=1` and a lot of requests to isolate single request processing and measure latency footpring,...

First part of investigation https://softwaremill.com/benchmarking-tapir-part-1/

Second part: https://softwaremill.com/benchmarking-tapir-part-2/. I'm closing this issue, as the investigation part is pretty much done.

I thought about it too, netty-future, possibly with jsoniter-scala.