Skip to content

7.5.1 Very serious performance problems #35917

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

Open
3419912225 opened this issue May 2, 2025 · 3 comments
Open

7.5.1 Very serious performance problems #35917

3419912225 opened this issue May 2, 2025 · 3 comments

Comments

@3419912225
Copy link

After version 7.5.1 and the number of online users reaches 100 at the same time, the process occupancy of mongodb and node.js will be very terrible, and it will always be around 100%, which is often stuck. Please check it carefully. I will not have this problem when I switch back to version 7.4.1. Version 7.5.1 simply can't support many users to use at the same time!

@Gummikavalier
Copy link

Gummikavalier commented May 3, 2025

No issues for us with 500+ active online users with RC 7.5.1. More detail is probably needed, as we run 4 concurrent instances (processes) on the host at the same time (meaning ~125+ users per process). You are probably running only one?

Years ago I did some testing and I was able to run 500 active users on a single process, but I haven't tested it recently. I may repeat that test next week when I get the chance.

Also one chance is that the problem is some specific malfunctioning message that triggers the issue in RC 7.5.1 but not in RC 7.4.1 on your instance. Such example from the past was a message that contained specific text in xml format, and that was fixed eventually.

@Gummikavalier
Copy link

Gummikavalier commented May 5, 2025

The test with over 500 users with a single RC process is ready. We didn't spot performance issues.

The CPU load was ~ 5 % lower compared to running with 4 processes on the same server; A drop in hourly graph from slightly under 20% average to 10 - 15% average. Depending on your scenario this may or may not be meaningful. (If you run a lot of processes that might cause higher overhead for database communication, for instance.)

@reetp
Copy link

reetp commented May 6, 2025

GridFS.

Stop using it.

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

3 participants