Editing Desk-size computers / Supercomputers / Mainframes
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 26: | Line 26: | ||
|Statistic Reliability | |Statistic Reliability | ||
|Exceeding 99.99999% uptime per year; individual components failing won't cause performance or capacity issues | |Exceeding 99.99999% uptime per year; individual components failing won't cause performance or capacity issues | ||
− | |99.999% to 99.9999% uptime per year; individual components failing may cripple performance or capacity, but won't affect current tasks | + | |99.999% to 99.9999% uptime per year; individual components failing may cripple performance or capacity, but won't affect current tasks |
|Poorly built ones could run into trouble every few hours under a high burden; unplanned downtime of proper prebuilt servers is around a few minutes to 1 hour per month; individual components failing always break all current tasks | |Poorly built ones could run into trouble every few hours under a high burden; unplanned downtime of proper prebuilt servers is around a few minutes to 1 hour per month; individual components failing always break all current tasks | ||
|Varies (usually less than 99.9999% per year) depending on SLAs and configuration; each node follows the failure model of regular PC-based servers; nodes failing may cripple performance or capacity, but won't affect current tasks | |Varies (usually less than 99.9999% per year) depending on SLAs and configuration; each node follows the failure model of regular PC-based servers; nodes failing may cripple performance or capacity, but won't affect current tasks |