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
Current design will not handle high request gracefully. That is due to the issue with serializing requests through the blockchain, causing request that came later to time out. We should use a queue like bullmq to separate the request/queueing vs the submitting to blockchain, then respond back on a streaming channel (HTTP stream).
Design
Build a stress test simulator for devnet and verify behaviors.
user request -> [queue] -> process on account A (nonce_A)
\--> process on account B (nonce_B)
|---> process on account C (nonce_C)
The text was updated successfully, but these errors were encountered:
Motivation
Current design will not handle high request gracefully. That is due to the issue with serializing requests through the blockchain, causing request that came later to time out. We should use a queue like bullmq to separate the request/queueing vs the submitting to blockchain, then respond back on a streaming channel (HTTP stream).
Design
Build a stress test simulator for devnet and verify behaviors.
The text was updated successfully, but these errors were encountered: