The problem you’ve got here is that, by using -mcProfile, the module __main__ is cProfile (the actual entry point of the code), not your script. cProfile tries to fix this by ensuring that when your script runs, it sees __name__ as “__main__”, so it knows it’s being run as a script, not imported as a … Read more
You’re profiling the process startup, which is why you’re only seeing what happens in p.start() as you say—and p.start() returns once the subprocess is kicked off. You need to profile inside the worker method, which will get called in the subprocesses.
EDIT: I’m expanding the answer to include a more polished example. I have found a lot hostility and misinformation in this post regarding threading v.s. async I/O. Therefore I also adding more argument to refute certain invalid claim. I hope this will help people to choose the right tool for the right job. This is … Read more
With cProfile you can also profile existing programs, without making any separate profiling script. Just run program with profiler python -m cProfile -o profile_data.pyprof script_to_profile.py and open profile data in kcachegrind with pyprof2calltree, whose -k switch automatically opens data in kcachegrind pyprof2calltree -i profile_data.pyprof -k For example profiling whole paster server and webapp would be … Read more