我们如何计算 24/7 网站的正常运行时间?

发布于 2024-07-24 16:28:04 字数 65 浏览 3 评论 0原文

当公司站出来声称99.98%时,他们是如何得出这个数字的? 这是唯一的 QoS 参数还是还有其他有用且重要的参数?

When companies come forward and claim 99.98%, how do they come to that number? Is that the only QoS parameter or are there any other useful and important parameters?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

烟沫凡尘 2024-07-31 16:28:05

有几个有用的 QoS 参数,尽管并非所有参数都像 99.98% 的正常运行时间一样容易测量,很容易得出 - 99.98% 的时间,您的服务器可用。 其他指标:

  • 它们支持什么类型的带宽? 如果这是一个共享管道并且他们有多个大容量客户端怎么样? 您不太可能从供应商那里得到诚实的答案。
  • 如果您使用共享主机,那么您将在盒子上进行什么样的资源竞争? 同样,这是竞争信息,因此您不太可能得到诚实的答复。
  • 每个应用程序的独立性如何? 即,如果共同托管的盒子上的另一个应用程序循环 MySQL,您的应用程序会受到影响吗?
  • 他们多久升级一次依赖项,这是否会影响他们 99.98% 的正常运行时间?

然后还有一些不完全与 QoS 相关的托管问题:

  • 他们会为您进行备份等吗?
  • 他们对查询的反应如何? 他们是否有保证的回复时间,例如从第一封电子邮件到第一次回复 3 小时,24/7?
  • 他们有效率吗? 他们是否在有效的时间内解决了问题? 快速的响应时间很好,让人感觉很好,但如果他们不解决问题,那就不太好了!
  • 当你提出问题但由于你自己的技术背景而略有偏差时,他们是否对你很耐心? :)

There are several useful QoS parameters, although not all are as easily measured as e.g. 99.98% uptime, which is easily derived - 99.98% of the time, your server is available. Other metrics:

  • What sort of bandwidth do they support? How about if it's a shared pipe and they've multiple high-volume clients? You're unlikely to get an honest answer to this from the vendor.
  • If you're on a shared host, what sort of competition for resources will you have on the box? Again, this is competitive information, so you're unlikely to get an honest response.
  • How independent is each application? i.e. if another application on a co-hosted box loops MySQL, will your app suffer?
  • How often do they upgrade dependencies, and does that affect their 99.98% uptime?

Then there are the fluffy not-entirely-QoS related hosting problems:

  • Will they do your backups etc.?
  • How responsive are they to queries? Do they have a guaranteed response time e.g. 3 hours from first email to first response, 24/7?
  • Are they efficient? Have they resolved issues within a useful timeframe? A quick response-time is nice and feelgood, but if they don't fix the problem, that's not quite so good!
  • Are they patient with you when you suggest issues, but due to your own technical background are slightly off-base? :)
烟凡古楼 2024-07-31 16:28:05

这意味着您每年的停机时间大约为 2 小时。 在 8760 小时内,可以放心地假设您的网站不会因为托管问题而损失太多流量或业务。

我会查看推荐或在线搜索该公司的评论以获取其他信息。

That means your downtime is going to be roughly 2 hours per year. Out of 8760 hours, it's safe to assume your website isn't going to lose much traffic or business because of problems in their hosting.

I would look at testimonials or search online for reviews of the company for anything else.

沒落の蓅哖 2024-07-31 16:28:05

正常运行时间是服务质量指标之一。 其他有趣的数字包括“平均修复时间”、“平均故障间隔时间”和其他服务恢复数字。 理想情况下,会有人每天 24/7 保持清醒并发出警报以修复故障,但大多数地方(最多)都会有保持清醒的人员 24/7 监控服务,并让值班工程师进行实际修复(至少在以下情况下)这是一个更复杂的问题),因此了解非工作时间服务(如果他们会告诉您)也是选择提供商的一个因素。

Uptime is one quality of service figure. Other interesting figures are "mean time to fix", "mean time between failures" and other service restoration figures. Ideally, there would be people awake and alert 24/7 to fix faults, but most places will (at best) have alert and awake people monitoring the service 24/7 and have on-call engineers to do the actual fix (at least if it's a more complicated one), so knowing how out-of-hours service (IF they will tell you) is also a factor in choosing a provider.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文