Is This Normal in VS 2005 ??

  • Thread starter Thread starter João Santa Bárbara
  • Start date Start date
J

João Santa Bárbara

Hi all
i have a few problems with my Visual Studio ide 2005 :(

is This normal ???
when i'm writing in the code page my cpu goes wild ( 100 % ) only writing
when i press save my CPU goes Wild ( 100% ) for a couple time
when i move a few controls in the designer it goes wild !!! and mouse
pointer starts to flick....

is this all normal ???


JSB
 
I have a 3.2GHz P4 with 1 Gig of memory and task manager does not show my
CPU above 30% when I type and I have outlook, media player, MSN IM, Yahoo
IM, and more then likely a few other items running. Most likely its
intelisense looking up values.

As for dragging tools onto a form it depends on if its the first time in a
while or I have been working on the form. The first time will jump the CPU
to 50ish % but after that there is not much impact.

The only time I have had a problem with saving is ASP.NET. I copied some
data from an HTML form to an ASP form and the first save can really drag
down the system. A couple times I had to kill VS because it went to never
never land.

Regards,
John
 
Yes, it is. It often freezes when trying to pop open a list of methods in
intellisense, and other similar things that really shouldn't be so tasking.
Probably more memory would help, but it's too bad that the newer and better
version of visual studio performs so horribly compared to its predecessor.
 
I too have noticed poor performance (which may have actually got worse since
applying hotfix 915038)

The devenv.exe process seems to be using an excessive amount of memory over
the course of a day's development. I'm not sure what the normal amount of
memory used by that process should be, but for instance in my current
solution it uses:
- 128MB upon opening the solution (no designers or code windows open)
- 190MB upon beginning debugging (say just by hitting a breakpoint)
- 185MB upon stopping debugging (surely this should return to near enough
128MB?!)
- If I open a form designer, add at least another 60MB to the above figures
(and closing the designer also does not recover the memory used)
- Over the course of a day, it can end up using as much as 900MB - surely
that can't be right?!

FYI, my solution consists of the following:
VB Windows app (using several 3rd party components e.g. ComponentOne
FlexGrid, DevExpress XtraNavBar, ActiPro Wizard)
4 VB Class Libraries
My machine: Dell Inspiron 9300, single 1.86 GHz processor, 1 Gb RAM, XP Pro
SP2

So my question is, is this normal behaviour / is it expected that the
process will consume more resources since applying the hotfix?

Richard
 
Hello Richard,

SP didnt helps u. it's normal. Debuggin load a lot of additional libraries,
pdb and etc, so memory consumed


RB> I too have noticed poor performance (which may have actually got
RB> worse since applying hotfix 915038)
RB>
RB> The devenv.exe process seems to be using an excessive amount of
RB> memory over
RB> the course of a day's development. I'm not sure what the normal
RB> amount of
RB> memory used by that process should be, but for instance in my
RB> current
RB> solution it uses:
RB> - 128MB upon opening the solution (no designers or code windows
RB> open)
RB> - 190MB upon beginning debugging (say just by hitting a breakpoint)
RB> - 185MB upon stopping debugging (surely this should return to near
RB> enough
RB> 128MB?!)
RB> - If I open a form designer, add at least another 60MB to the above
RB> figures
RB> (and closing the designer also does not recover the memory used)
RB> - Over the course of a day, it can end up using as much as 900MB -
RB> surely
RB> that can't be right?!
RB> FYI, my solution consists of the following:
RB> VB Windows app (using several 3rd party components e.g. ComponentOne
RB> FlexGrid, DevExpress XtraNavBar, ActiPro Wizard)
RB> 4 VB Class Libraries
RB> My machine: Dell Inspiron 9300, single 1.86 GHz processor, 1 Gb RAM,
RB> XP Pro
RB> SP2
RB> So my question is, is this normal behaviour / is it expected that
RB> the process will consume more resources since applying the hotfix?
RB>
RB> Richard
RB>
RB> "João Santa Bárbara" wrote:
RB>---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
Richard Bysouth said:
I too have noticed poor performance (which may have actually got worse
since
applying hotfix 915038)

The devenv.exe process seems to be using an excessive amount of memory
over
the course of a day's development. I'm not sure what the normal amount of
memory used by that process should be, but for instance in my current
solution it uses:
- 128MB upon opening the solution (no designers or code windows open)
- 190MB upon beginning debugging (say just by hitting a breakpoint)
- 185MB upon stopping debugging (surely this should return to near enough
128MB?!)
- If I open a form designer, add at least another 60MB to the above
figures
(and closing the designer also does not recover the memory used)
- Over the course of a day, it can end up using as much as 900MB - surely
that can't be right?!

FYI, my solution consists of the following:
VB Windows app (using several 3rd party components e.g. ComponentOne
FlexGrid, DevExpress XtraNavBar, ActiPro Wizard)
4 VB Class Libraries
My machine: Dell Inspiron 9300, single 1.86 GHz processor, 1 Gb RAM, XP
Pro
SP2

So my question is, is this normal behaviour / is it expected that the
process will consume more resources since applying the hotfix?

Richard
Click to expand...
What happens with a similar solution, but without the third party controls?
I ask because I just watch the memory use with a similar solution here, sans
third party stuff, and my memory figures are less than half yours.
 
Peter

I created a "Hello World" windows app, and noticed the following resource
usage for devenv.exe:
Open Visual Studio - 21 Mb
Create solution - 57Mb
Open form designer - 70Mb
Open code window - 113Mb
Run app - 116Mb
Debug (hit breakpoint) - 120Mb
Stop debugging and close all code / designer windows - 118Mb


So it certainly seems that the 3rd party controls take more resources, but
still the memory is not being "recovered" after debugging even for a simple
app like this.
No massive issue I know (can just restart VS), but just interested to know
if others experience this too.
 
Richard Bysouth said:
Peter

I created a "Hello World" windows app, and noticed the following resource
usage for devenv.exe:
Open Visual Studio - 21 Mb
Create solution - 57Mb
Open form designer - 70Mb
Open code window - 113Mb
Run app - 116Mb
Debug (hit breakpoint) - 120Mb
Stop debugging and close all code / designer windows - 118Mb


So it certainly seems that the 3rd party controls take more resources, but
still the memory is not being "recovered" after debugging even for a
simple
app like this.
No massive issue I know (can just restart VS), but just interested to know
if others experience this too.
Click to expand...
Here is what I get with a similar exercise, plus one more step;
Open 21 meg
Create 30 meg
Add controls + code and build 80 meg
Run to breakpoint 97 meg
Stop debugging 94 meg
*Minimize VS 2005 window 5 meg*
Reopen window 15 meg.
 
Back
Top