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
Just to keep track if things we may want to improve. Everyone is welcome to share your ideas!
Optimize MessageContext creation (for high-throughput scenarios): On every incoming message, a new, large MessageContext object is created, including numerous function closures (reply, progress, error, etc.). For the vast majority of applications, this is perfectly fine and leads to clean, easy-to-read code. However, in extreme high-throughput environments, the overhead of this object and closure creation for every single message could become a performance bottleneck. A potential optimization could be to use a reusable, per-connection context object that is simply updated with the details of each new message, rather than being recreated from scratch. This is a significant architectural change with trade-offs in complexity and is not a necessary change, but it's something to keep in mind for future performance tuning.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Just to keep track if things we may want to improve. Everyone is welcome to share your ideas!
MessageContextcreation (for high-throughput scenarios): On every incoming message, a new, largeMessageContextobject is created, including numerous function closures (reply,progress,error, etc.). For the vast majority of applications, this is perfectly fine and leads to clean, easy-to-read code. However, in extreme high-throughput environments, the overhead of this object and closure creation for every single message could become a performance bottleneck. A potential optimization could be to use a reusable, per-connection context object that is simply updated with the details of each new message, rather than being recreated from scratch. This is a significant architectural change with trade-offs in complexity and is not a necessary change, but it's something to keep in mind for future performance tuning.Beta Was this translation helpful? Give feedback.
All reactions