You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context and scope
Once #31 is implemented, individual Warp messages will be processed in their own goroutines, significantly increasing the overall application throughput when compared to the serial processing approach. However, there still remains opportunities to optimize the individual message processing jobs, targeting end-to-end single message latency. Some known examples include:
Reducing the number of blocking RPC calls to API nodes
Improving the locking logic on the inbound request handler singleton
#185 may provide insight into other bottlenecks that are good optimization targets. We should also explore tools such as flame graphs to identify hotspots.
The text was updated successfully, but these errors were encountered:
Context and scope
Once #31 is implemented, individual Warp messages will be processed in their own goroutines, significantly increasing the overall application throughput when compared to the serial processing approach. However, there still remains opportunities to optimize the individual message processing jobs, targeting end-to-end single message latency. Some known examples include:
#185 may provide insight into other bottlenecks that are good optimization targets. We should also explore tools such as flame graphs to identify hotspots.
The text was updated successfully, but these errors were encountered: