Visual Studio starts slower with ReSharper

Visual Studio starts very slow when ReSharper is installed. Especially it takes long when "Processing command bar "System".
I'm ok with this delay when opening a Solution, but it annoys when you open VS to quick edit XML/HTML file.

Configuration:
- Visual Studio 2005 Professional
- ReSharper 2.0 (build #249)
- P4 3 GHz, 2 Gb RAM

13 comments
Comment actions Permalink

The startup time has reduced dramatically in the latest two builds (253 and 254). You can get the latest build from the download page http://www.jetbrains.net/confluence/display/ReSharper/Download

0
Comment actions Permalink

James Hebben schreef:

The startup time has reduced dramatically in the latest two builds (253 and 254).


It is better but I would not use the word "dramatically".

Instead of 3 seconds without Resharper it still takes 25 seconds until
VS.Net 2003 becomes responsive with build 254 on my PC.

The problem is that Resharper initializes even when no project is active.

And even if you double click on C++ file Resharper will insist on doing
it's initialization stuff.

Danny
---

0
Comment actions Permalink

Hello Danny,

25 seconds is indeed a fair estimation of the current startup time. ReSharper
initializes just after
starting VS - this is controlled by the 'Startup' checkbox in Tools|Add-In
Manager. It doesn't matter
whether any solution is opened at the moment.

Do I understand correctly that you don't like that you can't immediately
open VS with a C++ file from
e.g. Windows Explorer and are annoyed by a delay because of ReSharper initialization?

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

James Hebben schreef:

>> The startup time has reduced dramatically in the latest two builds
>> (253 and 254).
>>

It is better but I would not use the word "dramatically".

Instead of 3 seconds without Resharper it still takes 25 seconds until
VS.Net 2003 becomes responsive with build 254 on my PC.

The problem is that Resharper initializes even when no project is
active.

And even if you double click on C++ file Resharper will insist on
doing it's initialization stuff.

Danny
---



0
Comment actions Permalink

Danny
Sorry to hear about your 25 seconds. That's no fun.

I get somewhat different results:
Xp Pro SP2, Dual 3.6Ghz, 3Gb RAM

VS2005 Pro R# 254 Startup time is approximately 10 seconds, after which I can open a project.

0
Comment actions Permalink

Hello James,

well, the difference in startup time may result from different hardware configuration.
Actually on my own
workstation (P4 HT 2.8 GHz, 2 Gb RAM) the startup time is approx the same
as on Danny's one.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Danny
Sorry to hear about your 25 seconds. That's no fun.
I get somewhat different results:
Xp Pro SP2, Dual 3.6Ghz, 3Gb RAM
VS2005 Pro R# 254 Startup time is approximately 10 seconds, after
which I can open a project.



0
Comment actions Permalink

Yes, you undestand correctly.

0
Comment actions Permalink

Hello Konstantin,

is it still a problem for you with 254?


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Yes, you undestand correctly.



0
Comment actions Permalink

Dmitry Shaporenkov (JetBrains) schreef:

Do I understand correctly that you don't like that you can't immediately
open VS with a C++ file from
e.g. Windows Explorer and are annoyed by a delay because of ReSharper
initialization?


Correct.

Thanks for the "startup" tip for disabling the automatic startup.

What's strange: if I open a project and re-enable Resharper it only
takes 5 seconds or so for Resharper to initialize. A second start of VS
2003 with Resharper disabled takes only 1 or 2 seconds, opening a
project then takes another couple of seconds, and re-enabling Resharper
takes about 5 seconds. Altogether not even 10 seconds, this is a lot
less than a start of VS 2003 with Resharper enabled and no project open.

Danny
---

0
Comment actions Permalink

Experiences vary I guess.. on my machine 254 did have a very dramatic improvement in start up time. Total time to start VS.NET 2003 and for it to become responsive went from about 30 seconds to under 6.

I won't say my specs 'cause they're not nearly as good as those posted above.. ;(

0
Comment actions Permalink

It starts much faster now - about 10 sec to open empty VS. Quite reasonable time for me. But still much slower than with Resharper disabled (about 2-3 sec).

0
Comment actions Permalink

Hello Konstantin,

yes, that's right. Certainly there is still some room for improvement in
startup time of ReSharper. But it's
unwise to expect VS with ReSharper to start as fast as without it -
loading ~60 ReSharper assemblies alone via Assembly.Load already takes more
than 2-3 secs. Perhaps we
should consider preJITting them for future...

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

It starts much faster now - about 10 sec to open empty VS. Quite
reasonable time for me. But still much slower than with Resharper
disabled (about 2-3 sec).



0
Comment actions Permalink

Dmitry,

Are all ReSharper dll's loaded at start-up? Would it be feasible in the future to load some on demand, particularly ones that are only occasionally used like unit test support, build script support, and asp.net support?

It would even be really nice if there was a configuration option to completely turn off certain features of ReSharper which could improve memory usage, performance, and help when there are bugs that reduce user efficiency/workflow (for example--I'd love to turn of build script support until the issues reported separately are all fixed).

Thanks,

Sam

0
Comment actions Permalink

Hello Samuel,

all ReSharper assemblies are loaded at start-up, although during work session
the user may load additional plug-ins. In theory,
it would be possible to load some assemblies (like Unit Test Support you
mentioned) on demand, but I have strong
doubts that resulting savings in startup time would compensate for the increase
of complexity.

Concerning disabling certain features, this is to some extent possible -
you can disable background analysis which
is sometimes slow on large files, you can disable auto-popups of IntelliSense
(code completion and parameter information).
But it is generally much better to fix bugs that annoy users than to introduce
options to disable functionality, and I believe
the case of build script support obeys this rule.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Dmitry,

Are all ReSharper dll's loaded at start-up? Would it be feasible in
the future to load some on demand, particularly ones that are only
occasionally used like unit test support, build script support, and
asp.net support?

It would even be really nice if there was a configuration option to
completely turn off certain features of ReSharper which could improve
memory usage, performance, and help when there are bugs that reduce
user efficiency/workflow (for example--I'd love to turn of build
script support until the issues reported separately are all fixed).

Thanks,

Sam



0

Please sign in to leave a comment.