Added 4 concurrency processes to legacy compose #348
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antoineludeau
force-pushed
the
antoineludeau/worker-concurrency
branch
from
c2c77e5 to
8aecbcb
Compare
antoineludeau
force-pushed
the
antoineludeau/worker-concurrency
branch
from
8aecbcb to
e0a54bb
Compare
nkokla
approved these changes
Dec 19, 2023
antoineludeau
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
To fix concurrency issues on new API (consumers can consume jobs in an order different than the order of the api calls), we are going to set pm2 to start only one worker.js process (modifying ecosystem.json)
Enhancement
In order to improve concurrency on the legacy "compose" this PR aims to switch concurrency number from 2 to 4 (everything will run on one node process).