이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

© 2024 Red Hat, Inc.