Hi Yun!
Thanks very much for sharing this information. Can I ask you to pull the
code in this branch:
https://review.openstack.org/#change,5762
And retry your test? On my test machines, the work that Huang Zhiteng
has done to convert Nova's servers to use multiple operating system
Both the profiling the multi-process work are great - good stuff!
Jay: Won't going multi-process just make it harder to profile? I think
it's actually a good thing to profile without the multi-process patch, find
fix and the bottlenecks in single-request performance, and then use
multi-process
On 04/12/2012 10:39 AM, Justin Santa Barbara wrote:
Both the profiling the multi-process work are great - good stuff!
Jay: Won't going multi-process just make it harder to profile?
Yep, that's why I said also note that your code profiling technique is
unlikely to be effective since cProfile
Just a small warning: since cProfile has its own overhead on entering/exiting
every method and uses deterministic rather than statistical profiling, it may
misrepresent tiny functions. They will take much more wall-clock time simply
due to the profiling overhead * number of executions.
I'm not
Hi Jay,
I will take a look later when I find a box with multiple cores to take
advantage it..
Agreed - cprofiling is not so useful this case. This would be a purely
performance benchmark. If implemented correctly, we should see a
notable gain. However, It will probably not that linear because we
Awesome, great stuff to know!
On 4/11/12 1:48 PM, Yun Mao yun...@gmail.com wrote:
Hi Stackers, I spent some time looking at nova-api today.
Setup: everything-on-one-node devstack, essex trunk. I setup 1 user
with 10 tiny VMs.
Client: 3 python threads each doing a loop of nova list equivalent
6 matches
Mail list logo
