Summary
According to JSON-RPC 2.0 spec
The Server MAY process a batch rpc call as a set of concurrent tasks, processing them in any order and with any width of parallelism.
However, we use jsonrpsee's defaults which don't apply any parallelism. So a batch of 100 eth calls (pretty common scenario) has to get through each call in the batch one by one. Most inefficient!
Completion Criteria
Additional Links & Resources
Summary
According to JSON-RPC 2.0 spec
However, we use jsonrpsee's defaults which don't apply any parallelism. So a batch of 100 eth calls (pretty common scenario) has to get through each call in the batch one by one. Most inefficient!
Completion Criteria
jsonrpseevia overrides in the middleware.Additional Links & Resources