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

Django: Siege issues #55

Open
CoolBlueSam opened this issue Aug 9, 2024 · 1 comment
Open

Django: Siege issues #55

CoolBlueSam opened this issue Aug 9, 2024 · 1 comment

Comments

@CoolBlueSam
Copy link

I noticed the issues with siege were put in the Django Readme: JoeDog/siege#4
However this issue was started in 2015 and last update was in 2023. When can we expect a fix. I have noticed the issues in my runs where the Django workload just stop after some iterations especially when I am specifying configuration that utilizes all the CPUs in the system. For working around I am using REPS as indicated in the documentation but given there is not update on siege github, I am curious if this will be ever fixed?

@excelle08
Copy link
Contributor

Replacing Siege with a more robust load generator is something on our list, though we haven't yet had time to work on it. Right now the best approach we would suggest is to use the Reps based method. We're not sure when the author of Siege will fix this problem (or if they will ever fix it) given the issue has been brought up long time ago and has active discussions around 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

2 participants