|
|||||
Which operating systems does the server support? What port and network interfaces dose it have
Futureproofing
How much expansion capability is available such as disk, memory, peripherals, etc?
ROI
Do you get your money's worth or are there better deals available?
Service
What warranties and service contracts are available? Can you get prompt service at a reasonable price?
We used WebBench v4.1 to test the server performance of each machine. For the Windows-based machines, we ran Business Winstone 2004 v1, Multimedia Content Creation Winstone 2004, and WinBench 99.
While most servers are not generally expected to be used for business applications, we thought running these tests on these hybrid machines -- that is a cross between a dedicated server platform and a decent desktop -- would show their relative performance at the very least. Especially look at the Altech: it is an AMD Athlon 64 desktop performance machine in a server chassis. None of these servers had SCSI disk drive units, all were either SATA or IDE type drives; some had a level of RAID functionality.
We could not run the Windows-based tests on the Xenon platform as it was running Linux. Multimedia Content Creation Winstone 2004 continually failed when run on the Altech server, therefore we could not record a score for that machine, likewise Business Winstone 2004 failed each time on the HP and we could not log a score.
Interestingly the major differences in performance between the Intel-based machines were perhaps due to their operating systems. The Xenon was running Red Hat Linux, the Acer was running Microsoft Windows 2000 Server, and the HP running Microsoft Windows Server 2003. The Xenon server's WebBench results, while quite consistent, were a little on the low side. This should not count against it necessarily; with a little bit of Linux and Apache tweaking, the user is bound to get results in the same ballpark as the other machines.
The Acer results running WebBench were both high and consistent. The HP's WebBench results looked promising initially but once it hit a 40 or 60 client load it dropped off dramatically, perhaps this was due to the operating system more than the server itself.





