Since my requests according to my profiling take around 0.065 seconds to
execute. I am really unsure of what happens after the response leaves the
django side and uwsgi starts handling it with nginx. Is there a way to do
some profiling at uwsgi or nginx level?
Best Regards,
*Rakan AlHneiti*
Find
now you **only** need to find the bootleneck :)
maybe its better to run ab from a machine in the same network
instead of running on the same machine, esp. with one core.
Rakan Alhneiti Wrote:
---
> Hello,
>
> Thank you all for your suppo
Hello,
Thank you all for your support.
*Mex: *
*1) is the setup of your vmware similar to you ec2 - instance? i talk esp.
about RAM/CPU-power here.*
Yes, i've setup the vmware machine to be 1.7 G in ram and 1 core just like
the small ec2 instance.
*2) do you have a monitoring on your instances,
Do you run the benchmark program on the same virtual machine as the web
stack?? For yielding conclusive results, you certainly don't want to
make ab, nginx, and all other entities involved compete for the same CPU.
If yes, try running ab from a different machine in the same network
(make sure
hello,
is the setup of your vmware similar to you ec2 - instance? i talk esp. about
RAM/CPU-power
here.
do you have a monitoring on your instances, checking for load/ram-zusage,
iowait etc?
maybe you should start your ec-test with less than 500 concurrent
connections and work up
to the point
