[issue3865] explain that profilers should be used for profiling, not benchmarking

Georg Brandl added the comment: Freshed up and committed in r85451. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue3865] explain that profilers should be used for profiling, not benchmarking

Sandro Tosi added the comment: Hello, Here's a patch that implement what's request by Fredrik. Regards, Sandro -- keywords: +patch nosy: +sandro.tosi Added file: http://bugs.python.org/file19188/issue3865-py3k.patch ___ Python tracker

[issue3865] explain that profilers should be used for profiling, not benchmarking

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list ma

[issue3865] explain that profilers should be used for profiling, not benchmarking

Fredrik Lundh <[EMAIL PROTECTED]> added the comment: (the reason this is extra bad for C modules is that the profilers introduce overhead for Python code, but not for C-level functions. For example, using the standard profiler to benchmark parser performance for xml.etree.ElementTree vs. xml.etr

[issue3865] explain that profilers should be used for profiling, not benchmarking

New submission from Fredrik Lundh <[EMAIL PROTECTED]>: You often see people using the profiler for benchmarking instead of profiling. I suggest adding a note that explains that the profiler modules are designed to provide an execution profile for a given program, not for benchmarking different l