05
10
2006
Microsoft Getting Started on Windows Web Hosting
Posted by: Lloyd Lopez in Daily Dose, The InternetLooks like Microsoft is now getting into web hosting. Windows Web Hosting is a subset of the complete Web hosting details found in The Microsoft Solution for Windows-based Hosting version 4.0. In order to help hosters quickly grasp the concepts and obtain practical experience in Windows-based Web hosting, Getting Started on Windows Web Hosting offers a simplified set of deployment and provisioning documentation, samples, and scripts for two basic Web hosting deployment scenarios.
Link: Microsoft
Entries (RSS)
October 5th, 2006 at 10:34 am
I still think servers with GUIs are a big waste of server CPU cycles and RAM. Ugh, the the tradeoff.
October 10th, 2006 at 5:55 am
Hello JP,
I have to agree with you on that however we need to consider that a casual user have no idea setting up their website on a server. CPU cycles is not really a concern unless you have a busy site like a forum that access the database frequently.
Regarding the RAM usage, there’s really a trade off but you still have options. As far as I know, on a LAMP server, CPanel uses a large chuck of memory. While it can run on a 128mb RAM, the minimum should be 256mb.
Plesk follows when it comes with memory usage while some folks say that Direct Admin uses the least memory (& CPU) recommend it on a low spec server.
On a Windows platform, I only know 2 control panels. SWsoft’s Plesk and Positive Software’s H-Sphere. I have no idea how big these two CP take resources on a server though.
October 11th, 2006 at 9:29 am
There’s my point. It’s a tradeoff, for performance against user-friendliness.
Because I can somehow manage a server without a GUI (and often found them less helpful or slower), it makes me think, “all that resources for this?”.
Imagine the specs needed by a Vista/Longhorn server. They’d still need a fancy video card. I just hope that there’s a way to run it only with the command prompt and completely disable the Explorer shell when running the server.
This is where I think that the Windows kernel design isn’t flexible enough because it is so bound to the Explorer shell. That is why there are problems porting them to smaller architecture/processors.