You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: