Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Ability to choose profiled files

See original GitHub issue

Description

I tested you package against django tests, after I saw what you were capable of doing using code heatmap, which renders great by the way. So I thought I would give it a try on my Django tests because selenium is taking long time, and a heatmap would definitely reveal what parts are slow so I can focus on them.

How to reproduce

$ vprof -c h "manage.py test --failfast"

Actual results

The code heatmap is only showing the manage.py file, would it be possible to add an option to monitor my test files (i.e. tests.py or any other file).

Expected results

I would like to have several files show up in the profiling result (that I pick beforehand)

Version and platform

vprof==0.36.1 MacOS 10.12.5 Python 3.5.2

Issue Analytics

State:
Created 6 years ago
Comments:14 (11 by maintainers)

Top GitHub Comments

2reactions

nvdvcommented, Aug 21, 2017

i’ve just pushed commit to master that enables code heatmap calculation for all running code, not just specified modules. Output might look noisy, but I am thinking about skipping standard library modules if that makes sense.

1reaction

nvdvcommented, Sep 1, 2017

Heatmap excludes code from libraries now. I think I will play with it some time before releasing, but it looks way better now 😄