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
Hello, I encountered certain obstacles in my use case while attempting to execute the molecular actions. Briefly, I have a service (gateway for the main app with moleculer-web) that looks like this :
external.call is located on another node and invocation happens using NATS transporter. By design actions hello and second_call are gonna be loaded to process unique tasks. Before publishing it to production I made benchmarks for each action and received such results on my laptop:
The hello action works pretty well, the result was ~600rps
But the second one second_call was very much degraded, I received just ~40rps
Also, I received similar results after deployment to a prod-like environment. I believe this occurs due to external triggering, which is anticipated, but why so much? I've tried to use different load-balancing strategies and bulkhead but didn't receive any significant improvements. Is there a possibility of configuring Moleculer to enhance this behavior or it's some kind of bug?
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.
Hello, I encountered certain obstacles in my use case while attempting to execute the molecular actions. Briefly, I have a service (gateway for the main app with
moleculer-web) that looks like this :external.callis located on another node and invocation happens using NATS transporter. By design actionshelloandsecond_callare gonna be loaded to process unique tasks. Before publishing it to production I made benchmarks for each action and received such results on my laptop:helloaction works pretty well, the result was ~600rpssecond_callwas very much degraded, I received just ~40rpsAlso, I received similar results after deployment to a prod-like environment. I believe this occurs due to external triggering, which is anticipated, but why so much? I've tried to use different load-balancing strategies and
bulkheadbut didn't receive any significant improvements. Is there a possibility of configuring Moleculer to enhance this behavior or it's some kind of bug?All reactions