Issue 99 in unladen-swallow: Profiling guidelines in wiki are important.

[unladen...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement

New issue 99 by khamenya: Profiling guidelines in wiki are important.
http://code.google.com/p/unladen-swallow/issues/detail?id=99

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



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[unladen...@googlecode.com]

Updates:
Status: Duplicate
Mergedinto: 63

Comment #1 on issue 99 by collinw: Profiling guidelines in wiki are
important.
http://code.google.com/p/unladen-swallow/issues/detail?id=99

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.

[unladen...@googlecode.com]

Comment #2 on issue 99 by khamenya: Profiling guidelines in wiki are
important.
http://code.google.com/p/unladen-swallow/issues/detail?id=99

OK, I see.

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

[unladen...@googlecode.com]

Comment #3 on issue 99 by collinw: Profiling guidelines in wiki are
important.
http://code.google.com/p/unladen-swallow/issues/detail?id=99

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.