openstack team mailing list archive

[Jay Pipes <jaypipes@xxxxxxxxx>]

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 wouldn't track the forked child 
worker processes' stacks" ;)

>   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 for great concurrent-request performance?

Agreed!

-jay