3 ms·
Also there are some traceability issues involved in using asynchronous APIs: "In the asynchronous style, each stage of a request might execute on a different th
by mikmoila 3y ago
Also there are some traceability issues involved in using asynchronous APIs: "In the asynchronous style, each stage of a request might execute on a different thread, and every thread runs stages belonging to different requests in an interleaved fashion. This has deep implications for understanding program behavior: Stack traces provide no usable context, debuggers cannot step through request-handling logic, and profilers cannot associate an operation's cost with its caller. "
https://openjdk.org/jeps/444 https://openjdk.org/jeps/444
- saagarjha 3y agoIn theory an async-aware runtime can stitch together a coherent and useful backtrace, but in practice most legacy tooling won’t :(
- ElectricalUnion 3y agoCollecting those potentially very expensive stack traces, specially in those highly concurrent environments with high throughput requirements would be great for debugging but probably is gonna kill the performance of the system. But it would be nice (even if as a very heavy hammer) as an option.