jesscoburn.com

Tidbits and thoughts on webhosting, web applications and just general cool geek crap.


I recently posted a blog entry about my ‘informal’ apples to oranges comparison of the different virtualization platforms available for windows. Apparently I didn’t spell it out clear enough that things were not on a level playing field.  Well, guys I did it. I went and pissed off Bob. Sorry Bob.

But Bob taught me a couple lessons:

first don’t post half a**ed comparisons without coming out and telling everyone they are half a**ed comparisons and making it blatantly obvious they are half a**ed. I thought I described the different hardware that I had available at the time and mentioned that I had a brand new server on the way to do a real benchmark. He’s 100% correct though so I’m saying it here:  Guys my benchmark from 10/1 is half-assed! There I said.  (but you can bet your a** I’m going to be very thorough in my next test using the same exact machine all running only ONE virtual instance!)

second, read the EULAs & PURs! (that’s End User License Agreement and Product Use Rights) before you go doing something stupid like creating a half a**ed comparison and posting your results on the Internet.  So basically don’t just click “I Agree” and run off installing that application.

So here’s what I learned:

1. VMware’s EULA states:

You may use the Software to conduct internal performance testing and benchmarking studies, the results of which you (and not unauthorized third parties) may publish or publicly disseminate; provided that VMware has reviewed and approved of the methodology, assumptions and other parameters of the study. Please contact VMware at benchmark@VMware.com to request such review.

Okay so I can share my results with others just I can’t publish them or publicly make them available. Seems like privately sharing my results is okay though?

2. Microsoft’s Product Use Rights (a 66 page word doc of legalese) says:

i. Software. You must obtain Microsoft


I’ve pulled the article until I have time to properly benchmark all three systems on identical hardware, hopefully after the holidays.  Although I used different hardware, I firmly believe my numbers provided a reasonable estimate of what performance you would see using identical hardware.   I’d had verbal feedback from others that in fact they saw similar results but nothing to substantiate those comments.

The differences between RAID, CPU’s, Drives, etc all tended to balance out in my opinion. I welcome anyone to take on this task as well as I’d love to have something to compare my numbers against and prove my numbers as wrong.  So put your money where your mouth is and let’s see what you got.

Virtual Server 2005 R2 & iSCSI


Microsoft has an article available regarding Virtual Server 2005 R2 and iSCSI. I've been digging around on the forums and it seems the only way to really get the performance out of this is by having the iSCSI storage on the actual host machine. I haven't played with it, don't know enough about it but I do know iSCSI is way cool and I'm dying to play with it. Here's the link: http://www.microsoft.com/downloads/details.aspx?FamilyID=d112aa63-a51e-4722-a41b-98b3ab3700a3&displaylang=en

So in the Virtual Server how to on setting up a 2 node cluster there was mention that you should select the SCSI drive emulatored because the IDE emulator was slower than the SCSI one and that this was true even if you were running on IDE disks. Strange, right? Virtual PC Guy recently wrote a new blog entry that really sums up the two versions of disks and why one over the other: http://blogs.msdn.com/virtual_pc_guy/archive/2006/02/06/525487.aspx So now you're going to run off, create a SCSI disk and install the OS and wait and wait and wait and start cursing me because my god is that install taking a day and night. By the time it's done though you'll install the emulator and lo and behold it's a ton faster now. What gives? Why was the install so damn slow?  It turns out that the SCSI drive isn't actually faster until you load the driver from the VM additions. So how do you get around this? Well, during install press F6 to load a 3rd party driver. If you go back to the Floppy disk in the machines configuration and and tell it to mount a known Floppy disk image you'll see there's one on there called something like "VM Additions SHUNT SCSI drivers" mount that bad boy and then go back to your install and have it read the drivers off of this disk. It will now use the VM additions SCSI drivers during the install and you won't have to wait 3 hours for the install to finish… This is a huge time saver… Oh and make sure you read that blog entry on the differences about the two and why SCSI versus IDE, it's a huge question that seems to get pounded time and time again.

Server Virtualization is becoming a major item these days and is many companies are adopting it. I've heard storys all over the place from development to production, from guys using it to setup test labs of multiple servers using only a handful of boxes to companies replacing 700 physical servers with less than 350. For the hosting industry I believe this technology is going to completely replace shared hosting and how we think of shared hosting today. SWsoft is one company who's server virtualization platform is already targetting hosting. The ability to move a virtual server to another physical server with almost zero downtime is simply awesome. Blah Blah Blah On to the goods. Microsoft has an outstanding article on Virtual Server Clustering that can be downloaded from: http://www.microsoft.com/downloads/details.aspx?FamilyID=09cc042b-154f-4eba-a548-89282d6eb1b3&displaylang=en If you're setting up virtual server, whether you plan to cluster it or not. I recommend you print out this article and read it thoroughly. It really does a great job of not only explaining the clustering setup but demonstrating just how powerful virtual server is and what can be done with it. Jess