Linked by David Adams on Wed 16th Apr 2008 15:35 UTC, submitted by R_T_F_M
Thread beginning with comment 310217
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-06
Surveys tend to be, err, inaccurate by design.
Numbers -can- very YonY.
Windows 2K3 might have had a -very- bad year: Microsoft possibly invested more resources on Win2K8 and Vista, taking them from the Win2K3 team; Hackers might have figured out how Win2K3 works and started exploiting it, etc.
By itself, the variation in numbers between surveys doesn't necessarily nulls the survey.
As opposed to Laura Didio, that is...
You simply HAVE to see statistical noise. Even more so this has to be true for uptime. Make a survey with 10000 responses, then we start talking about reliability.
While you might be statistically right, you're completely off mark here.
I work in the five-9's world. Both our software (that runs on a large number of servers - both RHEL and Win2K3) must be able to log ~6m of down-time per year. (Granted, I doubt that we are capable of achieving more then 4/9's - but that's something else...)
Look at it from my employer's perspective - 50% of our software solution is using Windows 2K3; According to this survey Windows 2K3 doesn't even come close to logging 3/9's while RHEL logs close to 4/9's. (~30m/y in our own experience - using a highly customized version RHEL5)
Given the basic requirement for 5/9's and these numbers (statistical noise or not), should my employer risk his head choosing Windows 2K3? Doubt it.
Analysts sell out without obviously seeming to do so, that is their business model.
I must agree.
As much as I like these numbers (and plan on using them to get my employer to port additional products to RHEL instead of Windows 2K3), Yankee group's survey have a -very- problematic history. (TCO/Get-the-facts)
- Gilboa
Edited 2008-04-18 04:20 UTC