Replies: 1 comment
-
Issue opened: #1237 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.call
is located on another node and invocation happens using NATS transporter. By design actionshello
andsecond_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:hello
action works pretty well, the result was ~600rpssecond_call
was 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
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?Beta Was this translation helpful? Give feedback.
All reactions