mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-25 23:15:51 +03:00
[GH-ISSUE #198] [PERF] High CPU consumption when load testing #1081
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#1081
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 @sujit-baniya on GitHub (Sep 18, 2020).
Original GitHub issue: https://github.com/hibiken/asynq/issues/198
Originally assigned to: @hibiken on GitHub.
I tried to do load testing and CPU for worker (above 100%), redis and clients were above 60%
https://www.dropbox.com/s/o38apit2ulb44cp/Screen%20Shot%202020-09-18%20at%2018.07.29.png?dl=0
@hibiken commented on GitHub (Sep 20, 2020):
Thank you for opening this issue.
CPU usage above 100% was most likely due to the worker process using more than one core on the machine.
With this simulated load, your Redis server is being slammed by many requests. Using redis cluster instead to balance the load across multiple instances may help.
I will look into a way to minimize the CPU usage by the package.