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
I read a bit about streams and spans. Streams are likely to work better when we have large chunk of data of variable sizes while spans work better with structured fixed-size data and the latter offers better performance enhancement, maintains concurrency in a better way.
What would you suggest is a better approach? I am currently not aware about the data that Abi encoding deals with.
Think how can you allocate as little as possible. For inspiration you can check how our Rlp Encoding/Decoding works with NettyRlpStream that is based on pooled memory.
Encoding and Decoding ABI allocates a lot, rewrite it to a version that will allocate a lot less (stream-like or spans?) and update usages.
The text was updated successfully, but these errors were encountered: