First of all I need to say I am completely amazed by the quality of this application considering it is a year from completion. I was happily surprised by the quality of the Windows XP beta 1 preview 3 years ago as well. However, I was not expecting anything
near the level of what was delivered this time around. I expected many things to be left out or incomplete. After using VWD Express for 2 hours I have but one complaint. The memory usage is HUGE. As soon as I started the application it swallowed 95 Megs. Then,
after some basic usage (going through the web-walk-through [http://beta.asp.net/GuidedTour/default.aspx]) it ramped up all the way to 157 megabytes. The site lists 128 as the minimum and 256 as recommended for system memory. I have 512, so I’m fairly ok. I’m
just scared to see how much ram I’d need for a project with a few hundred files in it, like the projects we’ve been developing for 2 years at work. Is it safe to assume the final product will be a bit better in memory consumption? I know this is only a Beta
1 release, so I’m not disappointed by the usage. I just wouldn’t be excited if the final release took that much ram. Other then the memory issue, which will most likely be taken care of, I really like VWD. In fact I would actually drop $100 to buy another
512 Megs if that’s what it took to move to VS 2005, although I feel many other people would not. There are so many things I have been saying over and over again with the old VS, along the lines of “I wish it did this” or “I wish it didn’t do that” that have
been fixed. I spent the first 2 hours playing to see what VWD could do and about every 10 minutes I found another feature I’ll sorely miss tomorrow at work. Overall, nice job! Ryan Riddell
Ryan, I have great interests to know what kind of operation you did that increased the memory usage. Could you be kind enough to narrow down and let us know? We do have some memory leakage problem in some specific areas which will be addressed in Beta2. For
example, you update web user control or web custom control and refresh or view switch the web form which hosts them. Thanks a lot! Yugang
I followed the VWD guided tour, although in a slightly odd fashion. I started out doing the master page section. I then went back to do the first 2 sections. Before I got to the data bound controls section (second in normal order, third in my order) the memory
was up to 157 Megs. The usage was fairly normal for the guided tour. However, I did spend a lot of time playing. For instance, I went between design and source view of the .aspx pages a lot just to make sure it would not change things. I also added a lot in
one view then checked the other to see the resultant formating. Although, it really wasn't more then what I'd do under normal development conditions. By the time I went to bed it was up to 185 megs of ram. I believe I still have it running at home. If I do
and there is a method to take a snapshot of the application state I would be willing to send that to MS for review. -Ryan
Yeah, I posted about this a few days ago. According to another ASP.NET Team member, the memory usage will certainly be lowered. However, not to the point of Visual Studio .NET 2003, as there will be many new features.
riddelrp
Participant
874 Points
175 Posts
Memory Usage...
Jul 01, 2004 01:04 AM|LINK
YugangW
Participant
1149 Points
227 Posts
Microsoft
Re: Memory Usage...
Jul 01, 2004 03:26 AM|LINK
riddelrp
Participant
874 Points
175 Posts
Re: Memory Usage...
Jul 01, 2004 12:34 PM|LINK
wswartzendru...
Participant
1615 Points
324 Posts
Re: Memory Usage...
Jul 01, 2004 07:23 PM|LINK