-
Notifications
You must be signed in to change notification settings - Fork 3k
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 web interface not starting on Windows #57
Comments
Hi! There seems to be an indentation error in the pasted code (compared to the example file). The output from running locust looks fine, so you should probably be able to just access http://localhost:8089/ Anyway, since you closed the issue, I assume you figured it out :). Btw, you should be fine using Locust on Windows while developing your tests. However, once you want to actually simulate a lot of users, I would strongly recommend running that on a Linux/Unix system (for example Ubuntu), since we've seen strange issues with gevent/windows when having lots of connections (I think this is Windows' fault and not gevent). |
Hey heyman, Thank you for the response, I felt a bit stupid as I figured out my issue literally moments after posting it -- after staring at it for some time, no less. About the Windows problems that sucks to here :( What sort of user load are you talking about where you start to see issues? Hundreds? Thousands? |
If I remember correcly (this was more than a year ago) we started seeing strange stuff when we got up to a couple of hundred requests per second. So with an average waiting time of 30 seconds, that would be a few thousand simultaneous users. I guess it also could have been something with that windows environment, so you could always try with more, but keep it in mind. Locust on linux is pretty well tested and should be quite stable though. |
The boring answer is "it depends". If you do a lot of CPU intensive work, like traversing and parsing HTML DOM it can affect greatly. Also, since Locust is event-driven I would advice not go above 80% CPU usage as it will throw off all timings when it gets saturated. |
Hi there, Here are details for my try: Unfortunatelly the http://127.0.0.1:8089 link does not display the locust web interface. Thank you |
I had the same problem. After hopeless searching, I tried navigating http://localhost:8089 and web interface appeared like miracle. Give it a try guys. |
i have the same issue on windows7. |
@konstantinosalvertis hi, did you close this issue? i am facing the same issue. |
@frostHit I don't know what that means. did you open a browser and try loading http://localhost:8089? btw, this issue was closed over 5 years ago. Please open a new one if you actually have an issue. |
@frostHit Hi, I couldn't find any workaround for the issue as I remember related to windows 7. Subsequently I set up a Linux server and locust worked fine. |
* change dependencies order in setup.py (locustio#54) * bugfix when hide edit modal while stopping and edit modal still open (locustio#56) * rizal new feature upload test file to eb (locustio#53) * upload test file to deployed eb * enable user to upload test file to deployed eb reload list on selector after file uploaded writing files to slaves distribute file to slaves and reload the test list route config json to user fileio update directories dinamycally reload after upload, populate directory list modify interface add confirmation dialog * fix non geometric elements * fix test not reloaded when not in master slave mode, css file and alert message * erlangga feature create new json keys (locustio#52) * Revert "erlangga feature create new json keys (locustio#52)" (locustio#57) This reverts commit acccdf5.
Strange http://127.0.0.1:8089/ doesn't work but http://localhost:8089/ does. |
...And then it never gets past this point. I am using the example locust file from the website for main.py
I am running Windows 7. Any ideas on what I could be doing wrong? Would be happy to clarify more information.
The text was updated successfully, but these errors were encountered: