Re:Visual profiler for Python
by dancsi on Thursday May 19, 2016 @02:34PM
(#11732502)
Is it just me, or running programs under PTVS slows them down by quite a bit? Even when I turn off debugging, it still seems to be slower than when I run the program from the terminal.
Re:Visual profiler for Python
by mdaniel on Thursday May 19, 2016 @03:58PM
(#11733265)
Just as an FYI, youtube links support a time bookmark at the end of the URL with `?v=CAFEBABE#t=11m0s` (in your example); the "share" widget on the site will encode the bookmark for you, if you prefer that method.
Re:Visual profiler for Python
by ghostly_s on Thursday May 19, 2016 @04:38PM
(#11733609)
As a Python learner, very excited to try this out on my code. I'm aware of other tools that can generate these visualizations but figuring out how to use them has seemed like a daunting task for someone like myself who barely understands what bytecode is; hoping this tool will serve as an accessible learning tool!
Re:Visual profiler for Python
by DiThi on Friday May 20, 2016 @04:12AM
(#11736249)
I mean the code coverage tool, not the flame graphs. To e.g. know what paths of the code are never executed. Chrome and Firefox already show flame graphs in their profilers.
Re:Visual profiler for Python
by kolapuriya on Thursday May 19, 2016 @03:05PM
(#11732812)
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.
Re:Visual profiler for Python
by vegabook on Thursday May 19, 2016 @04:14PM
(#11733411)
Looks like an awesome piece of technology, but why, whenever I see headline xxxx followed by "(github.com)" do I get a slight feeling of despair - that feeling that this project has a high chance of being future abandonware. Is it that having a proper, dedicated, expensive-looking, website, away from github, is a signal of access to resources, willingness to do proper marketing and documentation, and therefore, by correlation, longevity?
Re:Visual profiler for Python
by notifier2050 on Thursday May 19, 2016 @05:38PM
(#11734081)
Like with almost any open source project nobody promises you anything. But it's not framework, you don't lose much by not using it and you don't have to rewrite your code in case it would be abandoned.
Re:Visual profiler for Python
by vegabook on Thursday May 19, 2016 @05:52PM
(#11734167)
yes I realise that I'm looking a gift horse in the mouth, and I love git(hub), but I'm just pointing out that "(github.com)" might just be a net-negative marketing point for people looking for robust software.
[0] https://www.visualstudio.com/en-us/features/python-vs.aspx
edit: forgot link - https://www.youtube.com/watch?v=K-KqkFkp55k
DISCLAIMER: I'm an author of cProfile competitor, vmprof
[1]: https://bitbucket.org/sumerc/yappi/
[0]: https://www.youtube.com/watch?v=O1YP8QP9gLA
[1]: https://github.com/oxplot/crprof
First you start profiler in remote mode
and then use vprof.profiler.run function: (replace host and port if you run your webappp on another maching with address of machine you run "vprof -r" on).This will run profiler and send stats to server in JSON format.
(Ended up getting what I needed out of cProfile, which this also uses on the backend. Would've been nice to have the nice visualizations, though.)
When installing.
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.
Valgrind is essentially a VM, this uses cProfile - I wouldn't call that doing the 'same thing' at all.