-
Notifications
You must be signed in to change notification settings - Fork 67
vscode python debugger is very slow #2087
Comments
Well, the first thing would be checking if you have the accelerators modules there. To check, please provide the logs from running the debugger there -- it can be on a
i.e.:
|
Hi fabioz, thanks for your reply. the log output
|
Humm, it seems that the info on whether the accelerator modules are being used is not there as I thought it'd be (sorry about that). There's another way to get it though: Run (under the debugger) the code below and please provide the output.
|
Humm, it seems that the accelerator modules are forced to be disabled... I think the reason for that is historical and it should no longer be needed (I created a pull request to fix that: microsoft/debugpy#49). In the meanwhile, you can locally do that same change (basically commenting the |
I suppose you're talking about And I'm curious why I am still using
But I'm using ssh-remote, and in |
@karthiknadig do you have info on how to opt into the experiments with ssh-remote as @zehongs is doing? |
@zehongs it's really expected that depending on where you have the breakpoint things will run slower... still, I just double checked and there's one information missing in the DAP integration, which makes the debugger slower if there's any breakpoint in the same file and not in a particular function, so, I've created an issue to address that: microsoft/debugpy#51 -- note that this may not be as important if you use Python 3.7+ with the accelerator modules, but it does a big difference on pure-tracing (which would also be the case for PyPy), so, it's high on my priority list to fix that. |
@fabioz Thanks! |
@fabioz @zehongs This is currently a limitation, experiments cannot be set for the remote scenario. I will create a issue on the extension to support this. Created microsoft/vscode-python#10232 to address it. |
Since we have separate items tracking the underlying issues, I'm going to go ahead and close this one. |
Hi ptvsd team,
My code looks like...
By uncommenting
ptvsd.tracing()
, the script could be 10x faster (from about 50s to 5s). So the vscode debugger speed must have something to do with ptvsd, right?Can you improve its related performance? Or what should I do? I'm not adding this
ptvsd.tracing()
everywhere in my code :)The text was updated successfully, but these errors were encountered: