-
Notifications
You must be signed in to change notification settings - Fork 1k
Implement performance profiling #757
Comments
With transaction batching, I can get to 600 invokes/sec. My feeling is (given that the profiler does not show any big offenders) that the big speedbump is transaction execution latency to the chaincode and back. |
adding @dongmingh @bmos299... they have started profile work |
As suggested by @muralisrini, I tested with a noop chaincode, i.e. |
@corecode is this the throughput of a single client in closed loop or w. multiple clients saturating the system? |
system saturated, closed loop clients. |
Thanks. This number is very low on its own in the first place (although the rest of the system is not there yet). |
We need to implement performance profiling to understand (at any point in time) where the performance bottleneck in openblockchain is.
For example, at the time of opening this issue we are at about 500 tx/s peak throughput - which is way too low - yet it is not easy to tell where the bottleneck is.
Besides being able to identify throughput bottlenecks, we need also latency profiling capabilities.
The text was updated successfully, but these errors were encountered: