Seriously how old is your XP computer.
I recently bought a mid-level MCE XP pc, and I was concerned that the MCE functionality might slow down the system too much, but it has no effect on the peformance. In fact I've been able to record tv program's, burn a dvd, all while doing real dev work. I'm a dev for Microsoft by the way, but like I said, I'd expect all moderen OS's on reasonable hardware to do the same thing.
You still haven't awnsered the question, why are you implying you have to start a process for each request when creating services applicaitons?
IIS is a process, that starts once, and has different proction models for incoming requests request.
Is it really that much an advantage for processes to start faster on Linix, then they do on NT?
Process creation time is rarelly a serious bottle neck, but
creating effective multi-tasking programs is still very difficult, on any platform.
NT provides serveral multi-taksing choices, from threads, fibers ( a lite weight unix like process), processes, app contexts, and with.net, app domains, ( with a power permission assert model). Its been my experience that Windows provides every bit as many viable multi-tasking options as Linix. Windows challenge, and advantage, it there are so many RAD type VB developers creating apps with varying degress of quailty. Thats a refelection on the type of programmers, NOT the OS.
The whole point of the MS reasearch project is to determine if they can create an OS that is secure, stable, supports RAD, and is performant enough.
I'm curious to hear why your experience with it was so terrible. Seriously. I've worked on the Whidbey team and am always willing to listen to sugestions, even critism if they have a valid point. I'd also be interested to hear whats make you language of choic so much better then asp.net.
I hope Microsoft hits a home run with Indigo, and Avalon, and browser based clients finally start to the move to Smart Clients. Until now, its been too hard to write a good smart client on windows.
The whole point of xml being human reading, ie editable is off point. Its the fact that xml's structured format makes it more machineable, ie
you can write scpripts/programs that
read,write,query,update and validate much easier then you can a unstructured text file.
The truth of the matter is that for most small to moderate sites, Linx + Apache + php + mysql is a very powerfull, and afforable package.
One that Microsoft and IIS up until know has been hard pressed to beat. In the near future, with II7, Asp.net 2.0, and Sql Express, they are getting very close, and the MS platform aruguable would scale much better then a php based system.
Actually, at my last company we did have experts for both apache, and IIS.
On low in boxes, for simple services like static html, the preformance was similar, on high end multi-proc servers, IIS was signficantly more performant.
Belive it or not, W2K, and newer versions of NT have a very effective async threading module that gives them an advantage over Linx based WebServers. Apache is a great product, but it is seprate from LINIX, and Microsoft is getting better at intergrating IIS into newer versions of NT.
Actually configuration is an area that Microsoft puts a lot of effort into. As already mentioned in this theard, IIS 6 has a powerfull scripting interface that makes it is to easier to remote administer 100's or more IIS installs. IIS 7.0 goes even futher to make it even more seemless, and configurable. For you large cooporations these types of features are very important, and one of the reasons why IIS has a more of a presence for fortune 500 companies then they do for smaller sites.
A big problem for WebServers like IIS, and Apache is rouge modules that have there own thread pools that are behaving poorly.
Newere version of IIS take more controll over how modules are executing in IIS address space.
I'm sure Apache does the same.
Slashdot Mirror
Seriously how old is your XP computer. I recently bought a mid-level MCE XP pc, and I was concerned that the MCE functionality might slow down the system too much, but it has no effect on the peformance. In fact I've been able to record tv program's, burn a dvd, all while doing real dev work. I'm a dev for Microsoft by the way, but like I said, I'd expect all moderen OS's on reasonable hardware to do the same thing.
You still haven't awnsered the question, why are you implying you have to start a process for each request when creating services applicaitons? IIS is a process, that starts once, and has different proction models for incoming requests request. Is it really that much an advantage for processes to start faster on Linix, then they do on NT?
To imply any modern operating system can't multi-task zip in the back ground is just plain silly.
Process creation time is rarelly a serious bottle neck, but creating effective multi-tasking programs is still very difficult, on any platform. NT provides serveral multi-taksing choices, from threads, fibers ( a lite weight unix like process), processes, app contexts, and with .net, app domains, ( with a power permission assert model). Its been my experience that Windows provides every bit as many viable multi-tasking options as Linix. Windows challenge, and advantage, it there are so many RAD type VB developers creating apps with varying degress of quailty. Thats a refelection on the type of programmers, NOT the OS.
The whole point of the MS reasearch project is to determine if they can create an OS that is secure, stable, supports RAD, and is performant enough.
I'm curious to hear why your experience with it was so terrible. Seriously. I've worked on the Whidbey team and am always willing to listen to sugestions, even critism if they have a valid point. I'd also be interested to hear whats make you language of choic so much better then asp.net.
I hope Microsoft hits a home run with Indigo, and Avalon, and browser based clients finally start to the move to Smart Clients. Until now, its been too hard to write a good smart client on windows.
The whole point of xml being human reading, ie editable is off point. Its the fact that xml's structured format makes it more machineable, ie you can write scpripts/programs that read,write,query,update and validate much easier then you can a unstructured text file.
The truth of the matter is that for most small to moderate sites, Linx + Apache + php + mysql is a very powerfull, and afforable package. One that Microsoft and IIS up until know has been hard pressed to beat. In the near future, with II7, Asp.net 2.0, and Sql Express, they are getting very close, and the MS platform aruguable would scale much better then a php based system.
Actually, at my last company we did have experts for both apache, and IIS. On low in boxes, for simple services like static html, the preformance was similar, on high end multi-proc servers, IIS was signficantly more performant. Belive it or not, W2K, and newer versions of NT have a very effective async threading module that gives them an advantage over Linx based WebServers. Apache is a great product, but it is seprate from LINIX, and Microsoft is getting better at intergrating IIS into newer versions of NT.
Actually configuration is an area that Microsoft puts a lot of effort into. As already mentioned in this theard, IIS 6 has a powerfull scripting interface that makes it is to easier to remote administer 100's or more IIS installs. IIS 7.0 goes even futher to make it even more seemless, and configurable. For you large cooporations these types of features are very important, and one of the reasons why IIS has a more of a presence for fortune 500 companies then they do for smaller sites.
A big problem for WebServers like IIS, and Apache is rouge modules that have there own thread pools that are behaving poorly. Newere version of IIS take more controll over how modules are executing in IIS address space. I'm sure Apache does the same.