Profiling guidelines in wiki are important.

[GoogleCodeExporter]

Hi,

profiling the code based on JIT (especially LLVM) isn't that common case...

Could anyone put some guidelines in wiki, please? 
e.g. for oprofile?

well, I see some hints here:
http://groups.google.com/group/unladen-
swallow/browse_thread/thread/b8d822fc729d229c/096c0ea6041e9a72

Original issue reported on code.google.com by khame...@gmail.com on 16 Dec 2009 at 2:22

• Merged into: #63

[GoogleCodeExporter]

We to a slight patch to fully enable OProfile with Unladen; documenting that 
procedure 
before it works doesn't make any sense. Merging into that issue.

As for using oprofile in general, I recommend using Google: searching for 
[oprofile 
tutorial] brings up lots of pages, such as 
http://linuxtips.pbworks.com/Oprofile-
Tutorial.

Original comment by collinw on 17 Dec 2009 at 12:28

• Changed state: Duplicate

[GoogleCodeExporter]

OK, I see. 

What is the recommended profiling tool for u-s today?

Original comment by khame...@gmail.com on 17 Dec 2009 at 10:22

[GoogleCodeExporter]

You should use cProfile for general Python-level profiling (though that mostly 
disables 
machine code) or OProfile to profile the whole Python binary. After the 
necessary 
patches, OProfile will be the preferred way of improving performance of 
Python-the-
binary.

Original comment by collinw on 17 Dec 2009 at 5:02