-
Notifications
You must be signed in to change notification settings - Fork 6
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
match monolake http performance with nginx #116
Comments
MONOLAKE_BENCHMARK_PROXY_IP=172.31.2.253 (proxy service ip) |
@ihciah can you take a look at this issue, for small-size HTTP paylod Monolake is 20% less performance than Nginx |
@xiaosongyang-sv: nginx proxy has |
nginx proxy actually uses 4 workers and CPU usage is around 400%; server CPU is below 120%. |
With worker_processes auto, nginx can theoretically use more than 4 cores correct? For a fair comparison with 4c-monolake, we need to restrict the worker processes to 4 for nginx as well. |
The proxy runs on a machine with 4 CPUs so it most has 4 CPUs. I can change the nginx config but the result is same. |
An unrelated topic: It is recommended to bind all threads that can be bound to cores to obtain more stable test results. |
Makes sense. If the machine has 4 CPUs then it shouldn't be an issue for these results. But all users might not have 4 core machines (even though the readme suggests using one), better to change it to 4 here |
we need match monolake http performance with nginx. for current https performance results, monolake matches nginx. but for http, there is 20% - 25% gap:
|--------------------------|-------------------|--------------------|---------------------|--------------------|-------------------|--------------------|---------------------|--------------------|
monolake (proxy) config:
nginx server config:
[ec2-user@ip-172-31-22-170 ~]$ sudo cat /etc/nginx/nginx.conf
[ec2-user@ip-172-31-22-170 ~]$
nginx proxy config:
[ec2-user@ip-172-31-2-253 ~]$ cat monolake/benchmark/proxy/nginx/nginx.conf
[ec2-user@ip-172-31-2-253 ~]$
client (wrk2) for monolake:
we need find if we can improve monolake performance, either by configuration, or hardcode some default value in the code.
The text was updated successfully, but these errors were encountered: