此内容没有您所选择的语言版本。

4.5.2. Best Case Performance Scenario


At best, the overhead from virtual memory support presents a minimal additional load to a well-configured system:
  • RAM -- Sufficient RAM for all working sets with enough left over to handle any page faults[12]
  • Disk -- Because of the limited page fault activity, disk I/O bandwidth would be minimally impacted
  • CPU -- The majority of CPU cycles are dedicated to actually running applications, instead of running the operating system's memory management code
From this, the overall point to keep in mind is that the performance impact of virtual memory is minimal when it is used as little as possible. This means the primary determinant of good virtual memory subsystem performance is having enough RAM.
Next in line (but much lower in relative importance) are sufficient disk I/O and CPU capacity. However, keep in mind that these resources only help the system performance degrade more gracefully from heavy faulting and swapping; they do little to help the virtual memory subsystem performance (although they obviously can play a major role in overall system performance).


[12] A reasonably active system always experiences some level of page fault activity, due to page faults incurred as newly-launched applications are brought into memory.
Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

© 2024 Red Hat, Inc.