-
Notifications
You must be signed in to change notification settings - Fork 121
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
Running web-serving problem #100
Comments
Hi! Apologies for the delay in replying to you. From looking at your log output, it looks like you made a typo in specifying the web server's IP, here: |
Hi @yunjeongmun I have done more looking into this problem, and have managed to reproduce your results (with some different values). Here is what I got when running your commands (docker networks) on an OS X system.
I will take a look into this. Out of curiosity are you running on OS X or Linux? Docker bridge networking operates slightly differently on OS X. |
I'm running on Linux system. |
As you siad, I modified WEB_SERVER_IP=actual host ip address, and I used 80 port because of the error with port 8080:
So I added 'EXPOSE 80' in Dockerfile of db_server, faban_client, memcached server, and webserver to open port 80.
And I still got error messages.
And then, some running log like below..
And finally, I got error message as below
BUILD FAILED Total time: 14 seconds Thank you |
In the following command, the script bootstrap.sh has two optional arguments specifying the SQL container IP as well as the caching server:
You can find those instructions on the Web Serving section of the Cloudsuite website. So, in your case (using the host network) it would be something like:
However, in my tests the user session creation will still fail as before. I have managed to trace this problem to the generation of the file users.list, in the file UserGenerator.java. Currently I am testing a fix that I hope to finish soon. |
Thanks for your reply. Now, I successfully run web-serving benchmark.
Actually, I don't know why it works well.. And I have one more question, is it correct to increase 'LOAD_SCALE' value until CPU resources are full? |
I am not sure why adding a port publish has made this work for you. Since you are using the host network, there is no requirement to expose or publish ports explicitly. While the containers are running, can you post the output of running I am still testing the fix for running the client driver with docker networks, and will let you know when we have finished it. Regarding LOAD_SCALE, that controls the number of users that are simultaneously logging in to the web servers and requesting social networking pages. You can scale it up and down as much as you would like - keeping in mind that right now, you are running a single container as a client driver, and scaling the number of threads may start to stress the system. To tune the benchmark, we recommend testing your machines for the maximum possible request throughput, while maintaining your target QoS metric (we use 99th percentile latency). CPU utilization is less important than the latency and responsiveness for these benchmarks. |
Thanks for your reply!
I increase the LOAD_SCALE value 10 to 1000, and I got the Does Thank you |
Hello: For example, you have requested one machine to run 1000 user load generating threads (with that parameter of LOAD_SCALE), which likely will cause QoS violations. In order to "tune" the workload to properly model the behaviour of a frontend web server, you need to play with the system's parameters, such as client load mix, number of incoming requests, and latency constraints. Regarding the issue with Docker networks - I have figured out the reason why this happens, and will write a quick fix as soon as I can. |
I'm closing this for now. |
@Hnefi did you
@Hnefi did you ever create a fix for this? Do you have a patch I could try? Thanks. |
The docker network issue no longer exist. Please follow the latest document to run the workloads: https://github.com/parsa-epfl/cloudsuite/blob/master/docs/benchmarks/web-serving.md |
Hello, I'm struggling with runnging the Web-Serving benchmark. I need some help.
I ran below commands.. I created new network named network1
When I ran faban client, I got this warning message:
And finally:
Docker version: 1.12.5
Did I miss something in command line?
Thank you
The text was updated successfully, but these errors were encountered: