codeinabox@programming.dev to Programming@programming.devEnglish · 11 hours agoCan We Stop With the Uptime Percentages?blog.jim-nielsen.comexternal-linkmessage-square14fedilinkarrow-up149arrow-down15
arrow-up144arrow-down1external-linkCan We Stop With the Uptime Percentages?blog.jim-nielsen.comcodeinabox@programming.dev to Programming@programming.devEnglish · 11 hours agomessage-square14fedilink
minus-squarepHr34kY@lemmy.worldlinkfedilinkarrow-up43arrow-down1·11 hours agoMore simply, replace uptime with downtime. 99% uptime and 99.9% uptime seem close. 1% downtime and 0.1% downtime is clearly a 10x difference.
minus-squareHelloRoot@lemy.lollinkfedilinkEnglisharrow-up30arrow-down1·edit-210 hours agoWhy not just give hours/minutes per year/month?? I have no intuitive feeling for what 0.078% is, but if it says: “average downtime of 44 minutes per month” or “7h per year” it’s clear as day.
minus-squaretyler@programming.devlinkfedilinkarrow-up8·10 hours agoThat still isn’t as good as just saying the hours…
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up2·10 hours agoI dunno. As the article says, the people that use those numbers know what they mean.
More simply, replace uptime with downtime.
99% uptime and 99.9% uptime seem close.
1% downtime and 0.1% downtime is clearly a 10x difference.
Why not just give hours/minutes per year/month??
I have no intuitive feeling for what 0.078% is, but if it says: “average downtime of 44 minutes per month” or “7h per year” it’s clear as day.
That still isn’t as good as just saying the hours…
I dunno. As the article says, the people that use those numbers know what they mean.