Quentin Pradet

The three main contenders for parsing JSON are: * the standard json module, written in pure Python * orjson, written in Rust * as mentioned above, pysimdjson, a Cython wrapper...

A good test bed for pysimdjson support for extracting specific keys is this `parse()` function that currently uses ijson and is crucial to avoid client-side bottlenecks: https://github.com/elastic/rally/blob/master/esrally/driver/runner.py#L736-L792

@berglh Thanks for the report! It's true that you should always check that the client is not the bottleneck. Until we fix https://github.com/elastic/rally/issues/1399, would you mind running https://github.com/benfred/py-spy on one...

I opened https://github.com/elastic/rally/issues/1566 so that this issue stays focused on pysimdjson.

Thanks! Interesting. If it's not too much work, would you mind trying again with thespian debug logs activated and share the output?

Thanks a lot! The only information left I need to report the bug to Thespian would be the same logs but on thespian 3.10.6. Also, why specifically `192.168.20.6`? Is it...

For what it's worth I'm seeing `Warn no system has compatible capabilities for Actor esrally.racecontrol.BenchmarkActor` on Linux too. Comparing the logs between Thespian 3.10.6 and 3.10.7 would help a lot.

I reported the issue upstream: https://github.com/thespianpy/Thespian/issues/70

Right now if anyone faces the issue I'd recommend to apply the local workaround until we hear more from the Thespian side.

Hello, and thanks for considering Rally for your Elastic Agent benchmarking needs! I'll have to discuss more with the team, but it does look like at first sight that with...