ubuntu 服务器的正常磁盘读/写值
您如何确定在 ubuntu/linux 服务器的 I/O 活动上设置警报的最大值，该服务器托管最多 4 个运行 apache、mysql 和最多 4 个 tomcat 的站点？ 或者一般来说（如果有的话）在具有 7.2K SATA HDD 的生产服务器中，每秒 I/O 读/写的合适操作范围是多少？
我想要了解的是，如果每秒读/写达到峰值，对磁盘的影响。 我应该在磁盘/驱动器的规格中寻找什么来确定这一点？
正如你所看到的，我“显然”很困惑。 任何帮助/指导将不胜感激......
How would your determine a max value to set an alarm on the I/O activity of a ubuntu/linux server hosting upto 4 sites running apache, mysql and upto 4 tomcats?
Or in general (if there is one such) what is a suitable operational range for I/O read/write per second in a production server with a 7.2K SATA HDD?
What I'm trying to understand is the impact on the disks if read/writes per second peaks. What should I look for in the specification of the disks/drives to determine this?
As you can see, I'm "clearly" confused. Any help/direction would be appreciated...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您所担心的预期问题的价值比您必须注意警报的价格更高。
那是什么号码？ 这取决于很多因素，包括：
您想避免哪些问题？
您担心性能吗？ 如果是这样，您更担心延迟还是吞吐量？ 交互式和批处理作业性能之间的权衡如何？
您是否担心介质的磨损和使用寿命？ 您是否担心需要多久恢复一次备份？
您是否担心磁盘的价格？ 更好的磁盘将为您的运营带来多少价值？
写入可以延迟多少？ 通过缓存可以防止多少读取？ 对于独立性（ACID 中的 I）你能松懈到什么程度？
如果您确实想要最适合您情况的磁盘，那么您可能想问自己以下一些问题。 如果我处于您的情况，我可能会从低到中低价格范围中随机选择一个磁盘，然后看看它的效果如何。 然后你就会有经验可以学习，这样你就知道下次要做什么不同的事情（如果有的话），而且这不会花费你太多钱。
The value at which the expected problems you're alarming about are more expensive than the price of you having to pay attention to the alarm.
What number is that? That depends on a lot of things, including:
Which problems are you trying to avoid?
Do you worry about performance? If so, do you worry more about latency or throughput? How's the tradeoff between interactive and batch-job performance?
Do you worry about wear-and-tear and the lifespan of the media? Do you worry about how often you have to restore backups?
Do you worry about the price of the disks? How much value is better disks going to bring to your operation?
How much can the writes be deferred? How much reading is preventable through caching? How lax can you be with respect to independence (the I in ACID)?
If you really want the best disk for your situation, these are some of the questions you probably want to ask yourself. If I were in your situation, I'd probably pick a random disk from the low to low-mid price range, and then see how it works out. Then you'll have experience to learn from so you know what to do differently next time (if anything) and it's not going to cost you much.
当心linux，你将在内存中缓存一些数据（这很酷，因为它很快，但这会破坏你的基准测试）。
恕我直言，您不应该测试硬盘吞吐量，就好像数据将紧密地积累在物理磁盘上一样，您将会有更多，数据碎片也会影响结果......使用其他一些指标。
在顶部，您有一个“0.0%wa”统计数据，告诉您处理器在等待数据上花费了多少费用。 如果这个值变高，你就有麻烦了（你可以制作一个 RAID 阵列来增加吞吐量）。 我不知道top是如何得到这些信息的，但我打赌你也能得到它。
Beware of linux, You will have some data cached in memory (and it's cool because it's fast, but this will break Your benchmarking).
IMHO You shouldn't test the hdd throughput, as if the data will be accumulated closely on the physical disc, You will have more, fragmentation of data impacts result too... Use some other metric.
In top, You have a "0.0%wa" statistic that tells You how much the processor is spending on waiting for data. If this gets high, You are in trouble (You could make a RAID array to increase the throughput). I don't know how top gets this info, but I bet You could get it too.