Closed gavin-norman-sociomantic closed 6 years ago
There's already a simple per-request stats tracker in the client: https://github.com/sociomantic-tsunami/swarm/blob/v5.x.x/src/swarm/neo/client/requests/Stats.d#L31-L51, but it only includes overall average handling time, not the time-bucket per-request timing that the node has.
The current per-request stats tracking is also on a whole request level, not on a per-transaction (sub-request) level.
Similarly to how it works in the node, this would only make sense for one-shot requests (i.e. not for streaming or batch requests).
Updated issue description with latest info.
We already have request timing stats on the node side, but nothing on the client side.
There's already a simple per-request stats tracker in the client: https://github.com/sociomantic-tsunami/swarm/blob/v5.x.x/src/swarm/neo/client/requests/Stats.d#L31-L51, but it only includes overall average handling time, not the time-bucket per-request timing that the node has.
For one-shot requests, time-bucket stats would probably be useful for analysing performance problems. (Timing stats are generally not of use for stream or batch requests.)