Yes, I posted earlier (along with several others) that 220 appeared to be busy in the background running something all the time, CPU usage was around 50% and Dev Studio was sluggish. This is no longer occurring in 221, yay!
I'm suffering from perf problems with 221. If I open a moderate sized solution (5 projects, a few hundre files, 2 or 3 really large 5000+ lines files of constants, enums, etc) I see a constant 11% CPU usage by devenv.exe (VS 2003). I just did a simple test where I open this solution, build, then open a single file (200+ lines) and hold down the Down Arrow. The cursor stops about every 15-20 lines for maybe 1/2 second. This happens all the way to the bottom of the file.
Sadly the perf was driving me nuts so I uninstalled and am back on 1.5. Got a deadline today but I'll be back.
Have you expirienced any performance problems in 219-220?
--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"alastair" <no_mail@jetbrains.com> wrote in message
news:6714997.1141751421315.JavaMail.itn@is.intellij.net...
Yes, I posted earlier (along with several others) that 220 appeared to be busy in the background running something all the time, CPU usage was around 50% and Dev Studio was sluggish. This is no longer occurring in 221, yay!
I'm suffering from perf problems with 221. If I open a moderate sized
solution (5 projects, a few hundre files, 2 or 3 really large 5000+ lines
files of constants, enums, etc) I see a constant 11% CPU usage by devenv.exe
(VS 2003). I just did a simple test where I open this solution, build, then
open a single file (200+ lines) and hold down the Down Arrow. The cursor
stops about every 15-20 lines for maybe 1/2 second. This happens all the
way to the bottom of the file.
Sadly the perf was driving me nuts so I uninstalled and am back on 1.5. Got
a deadline today but I'll be back.
"alastair" <no_mail@jetbrains.com> wrote in message
news:6714997.1141751421315.JavaMail.itn@is.intellij.net...
Sadly I'm seeing this now too, it's better than 220 but not as good as 219, it really struggles with large files, 4,000+
Yeah... a little better than 220 but it still happens.
Nat