in

ASP.NET Weblogs

Dan Bright's .NET Weblog

The trouble with Longhorn...

It seems that I am not the only one who had a less-than-desirable experiance with the Longhorn bits.  I was running this on my main machine, a P4 3.0Ghz 800Mhz FSB with a gig of ram, 512 of which I had given to VPC.  It was horribly slow.

Whats worse, I had installed the 1.2 framework on my main machine, only to find that it took somewhere between 5-30 seconds for IIS to serve up any .NET content at all.  This was only compounded if accessed remotely.

So now here I sit, typing from a freshly repaved machine...  That will teach me to play with the bleeding edge.  I can't wait until I get my other motherboard back so I can set up a testing server without frustraiting myself to death.

Published Nov 06 2003, 04:15 PM by DanB
Filed under:

Comments

 

Jason Nadal said:

The trick is to install all of your applications on a striped RAID :) Runs very fast, with the exception of the hit for explorer.exe on startup. I just wish Longhorn itself would install on my RAID.
November 6, 2003 4:51 PM
 

scottgu@microsoft.com said:

Hi Dan,

Did you install the Whidbey bits on the Longhorn machine or another Windows version?

You shouldn't have seen Whidbey perf problems like above (we have some perf work left -- but not 5 seconds for each request <g>) on existing Windows versions.

Hope this helps,

Scott
November 6, 2003 4:59 PM
 

Dan Bright said:

Jason: Everything was installed on a striped SATA array, thats why I was so shocked.

Scott: I was running it on Server '03 Enterprise with all Windows Updates installed.

I'm not positive that the existance of VPC on the machine didn't have anything to do with these performance issues...

November 6, 2003 6:27 PM

Leave a Comment

(required)  
(optional)
(required)  
Add
Terms of Use