Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unit affects the performance of Node.js operations with Redis #1297

Open
dbit-xia opened this issue Jun 3, 2024 · 1 comment
Open

unit affects the performance of Node.js operations with Redis #1297

dbit-xia opened this issue Jun 3, 2024 · 1 comment

Comments

@dbit-xia
Copy link

dbit-xia commented Jun 3, 2024

Hello, I'm using Node.js 8/12 and after running with unit for several hours, I encountered a strange issue.
When not using unit, executing Redis commands consecutively with await 400,000 times only consumes 0.3 CPU cores and completes in 3 minutes.
However, when using unit, the same operation uses 1 full CPU core (100%) and takes more than 30 minutes to complete.

I've repeatedly confirmed that this issue is related to unit, but I don't understand why unit is affecting Redis operation performance.
During the testing period, only one Node process was running, and there was no significant difference in memory usage.
Could you suggest some directions for troubleshooting this?

Version: 1.32.1
Os: docker debian:bullseye-20240513
redis module: 2.8.0

@ac000
Copy link
Member

ac000 commented Jul 12, 2024

When not using unit,

Does this mean when Unit is not running?

However, when using unit,

Does this mean when Unit is running?

the same operation uses 1 full CPU core (100%)

What is using the CPU? Unit, Redis, something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants