Linked by David Adams on Wed 16th Apr 2008 15:35 UTC, submitted by R_T_F_M
Thread beginning with comment 309886
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Using this measurement...
by mdoverkil on Wed 16th Apr 2008 17:22
in reply to "Using this measurement..."
RE: Using this measurement...
by Ikshaar on Wed 16th Apr 2008 18:12
in reply to "Using this measurement..."
Well the downtime encompass the fact that server was down and the time it took to bring it back up. So no user-friendliness excuse... which would be questionable anyhow - I find my system very user-friendly to me
If your IT does not know how to fix his server, change IT.
RE: Using this measurement...
by lemur2 on Wed 16th Apr 2008 23:22
in reply to "Using this measurement..."
Downtime average per year may not always be a true test of the OS.
Windows/Linux tend to run on diverse hardware. Some without hotswap drives and such so harware failures could account for the downtime. Vs. the Big Unix systems which have hot swap drives and failover systems, build in at the hardware level.
Also the Userfriendlyness plays a role too, not the actual program reialability. So if it goes down how easy is it for the expert to fix the problem.
Windows/Linux tend to run on diverse hardware. Some without hotswap drives and such so harware failures could account for the downtime. Vs. the Big Unix systems which have hot swap drives and failover systems, build in at the hardware level.
Also the Userfriendlyness plays a role too, not the actual program reialability. So if it goes down how easy is it for the expert to fix the problem.
Downtime average per year may or may not be a true test of the OS ... but it is a true test of downtinme average per year.
If you are running a server, and you want it to be reliable, what you want to know about is ... downtime average per year.






Member since:
2005-09-27
Downtime average per year may not always be a true test of the OS.
Windows/Linux tend to run on diverse hardware. Some without hotswap drives and such so harware failures could account for the downtime. Vs. the Big Unix systems which have hot swap drives and failover systems, build in at the hardware level.
Also the Userfriendlyness plays a role too, not the actual program reialability. So if it goes down how easy is it for the expert to fix the problem.