2
Vote

Project load time

description

Hello,

I would like to congratulate you for your effort and the pytools product!
I have a django project of 29+ django apps (150+ models). When I open the project the load time takes about 5+ minutes.

I am using vs 2012 pro,django 1.4.3 and python 2.7 on a I7-2720QM CPU (2.2GHz) with 8GB RAM and samsung 840 SSD disk. Everything runs from the SSD disk

comments

jpetrick wrote Nov 20, 2013 at 9:04 AM

I have a similar problem with a VS 2010 Pro .sln that contains about 20 python 2.7 projects. It takes about 2 min to load and then editor performance is so laggy that it's very frustrating to use, not to mention outright crashing Visual Studio after long editing sessions (3 crashes in 3 hours).

I have disabled all the other extensions I typically load, so I'm fairly certain PTVS is the problem.

PTVS 1.5 did not exhibit these issues. When I have a bit more time I'll try to narrow down a repro case.

Zooba wrote Nov 20, 2013 at 4:02 PM

Hi jpetrick,

We've recently taken some improvements to project load time (contributed by an external developer), and if you're willing to take risks then these will be available in our next dev build (should be out by the weekend, but no guarantee - we have many other things going on this week).

I wonder, are the crashes related to out of memory errors? You should be able to look in Event Viewer and see the crash information (and maybe even a stack trace). If this is the cause, then I completely understand what the problem is - not that that means it is easily fixable, unfortunately.

How much better does it work with projects unloaded? You'll probably lose cross-project IntelliSense for the unloaded ones, but it should work around the memory issues.

iakovos wrote Nov 21, 2013 at 7:57 AM

Any solution to my first post's problem? I think it has to do with pytools + GIT because the initial project load times are getting really high without adding that many new code in the project but debugging existing one... we are at >15 mins now... (.git folder is not included in the VS project)

Zooba wrote Nov 21, 2013 at 3:49 PM

If it's simply the time taken to open projects initially, then you should see a pretty significant improvement with our next dev build, especially if you have a lot of files in each folder (as opposed to a lot of folders with small numbers of files in each).

If you're also seeing problems while editing, then we don't have a specific solution for that yet, but we're always making little changes to improve things.

Visual Studio has also made performance improvements in VS 2013, so if you have the opportunity to upgrade then you may also see some difference there.

jpetrick wrote Nov 21, 2013 at 10:43 PM

We'd love to upgrade to 2013, but last time I checked Xbox 360 development tools only work on 2008/2010.

Zooba wrote Nov 22, 2013 at 4:29 PM

jpetrick - I've looked into the info about the crashes that you sent me and they seem to be unrelated to PTVS. We've seen a lot of similar reports but there doesn't appear to be a clear cause. Also, being in VS 2010, it's unlikely to receive a fix at this point, so there's really not much I can do to help.

When I get a chance I'll try and replicate your scenario and see if I can identify the performance issues. There won't be a dev build this week, unfortunately (we can't fully automate the process, since we're still bound by Microsoft's release procedures).