[kolapuriya]

KCacheGrind relies on using valgrind, which gives you extremely detailed information on runtime information by wrapping your execution context at a very low level. For this reason, it can track individual memory allocations, function call statistics, etc. However, for Python, that can be a bit overkill; usually you're just looking to measure what parts of your code are taking up executing time and heap space.

This package uses cProfile, psutils, and pstats go get runtime information on your code as it's running. It's doing what valgrind does but in a much "higher-level" fashion, in pure Python. This means that it can give you more relevant information about your Python code.

[forgotpwtomain]

> It's doing what valgrind does but in a much "higher-level" fashion, in pure Python.

Valgrind is essentially a VM, this uses cProfile - I wouldn't call that doing the 'same thing' at all.

[_yosefk]

Actually KCachegrind displays files in an open format and is great for visualizing profiling info obtained from other tools.