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

Locust --processes argument generating multiple html reports #2639

Closed
2 tasks done
Hchanni opened this issue Mar 17, 2024 · 4 comments
Closed
2 tasks done

Locust --processes argument generating multiple html reports #2639

Hchanni opened this issue Mar 17, 2024 · 4 comments
Labels

Comments

@Hchanni
Copy link

Hchanni commented Mar 17, 2024

Prerequisites

Description

I'm running Locust in a docker container with the command within ECS, and it works well, I push the html report contents to S3, but for some reason, it's providing me with 5 files instead of just one. It seems that I'm getting a file for each worker, and then the master aswell.

Command line

locust -f ./locustfile.py --headless --processes 4 --users 150 --spwan-rate 150 --run-time 15s --host --html /tmp/report.html

Locustfile contents

Just a very basic hello world api endpoint.

Python version

3.11

Locust version

Locust docker image 2.24.0

Operating system

Linux

@Hchanni Hchanni added the bug label Mar 17, 2024
@cyberw
Copy link
Collaborator

cyberw commented Mar 17, 2024

Interesting. Is it not the same if you launch worker processes individually?

@Hchanni
Copy link
Author

Hchanni commented Mar 17, 2024

Interesting. Is it not the same if you launch worker processes individually?

When you mean launch worker processes individually do you mean in it's own seperate ECS task?

It's really weird because I run the Locust script through direct Github Actions with the html report essentially the exact same command above, and I only get one html report.

I also have run a distributed environment where worker tasks run in a separate ECS environment, and that runs with the UI and I can download the one specific HTML script.

@cyberw
Copy link
Collaborator

cyberw commented Mar 18, 2024

Interesting. Is it not the same if you launch worker processes individually?

When you mean launch worker processes individually do you mean in it's own seperate ECS task?

I mean by running locust … --worker 4 times instead of using --processes. I dont know that much about ecs tasks :) maybe run locally on your own machine first to remove it from the equation.

It's really weird because I run the Locust script through direct Github Actions with the html report essentially the exact same command above, and I only get one html report.

Weird indeed…

@Hchanni
Copy link
Author

Hchanni commented Mar 19, 2024

I've decided to go the distributed way of using --expect_workers and then spawning up multiple workers.

@Hchanni Hchanni closed this as completed Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants