mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 07:25:56 +03:00
[GH-ISSUE #530] [QUESTION] Does Concurrency parameter only work on same Golang process? #2273
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#2273
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rendybjunior on GitHub (Aug 27, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/530
I tested
Concurrency: 1configuration, and then I run multiple worker processes on different terminal tab.The result of my experiment, the concurrency configuration only work for each process, but NOT across processes.
Is this observation accurate? Because the documentation does not explain much about the concurrency.
If the answer is yes, concurrency only work on each process, then if I have multiple workers running on different pods (let say 5 pods) with setting
Concurrency: 1, this means I will have 5 concurrent tasks running.Hope the question is clear enough. Thanks! @hibiken
@hibiken commented on GitHub (Aug 31, 2022):
Yes, your observation is correct.
The concurrency option controls how many active goroutines a
Servercan have.