Skip to content

Parallel execution of tests causes lot of pressure on RP DB #159

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
nishant-shah-social opened this issue Apr 10, 2025 · 3 comments
Open
Assignees

Comments

@nishant-shah-social
Copy link

Hello,
We have around 5K+ tests and are running them in parallel with 12 workers. This is causing lot of pressure on report portal DB (self-hosted) and utilization spikes upto 100%, resulting into report portal calls being timed out during the test execution and results not reflecting correctly.
We do have decent enough resource limits for our DB:-
CPU :- 2
Memory:- 5GB
SSD Storage:- 250GB
The DB is hosted in GCP CloudSQL

Is there something that can be done?

Regards,
Nishant Shah

@AmsterGet
Copy link
Member

Hello @nishant-shah-social !
Which reporting endpoint are you using?
api/v1 or api/v2?
I believe api/v2 is more preferable for your case, as it works asynchronously on the server side (via a message broker) and offers higher bandwidth for requests.
Adding @irynakozak2 to check your setup.

Please let me know if this helps!

@irynakozak2
Copy link

Hi @nishant-shah-social ! I suggest doubling the size of CPU/RAM for your database (4 CPU/16 GB RAM) and adding more CPU for the ReportPortal itself to effectively handle your workload.

@nishant-shah-social
Copy link
Author

Thanks @AmsterGet ! We are using api/v1. Will try changing to api/v2

Thanks @irynakozak2 for the recommendation. I will try boosting up the resources as suggested.

@AmsterGet AmsterGet self-assigned this Apr 11, 2025
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