Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

virtual-host: More aggressive writeback of dirty #448

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Red54
Copy link

@Red54 Red54 commented Jun 17, 2022

vm.dirty_ratio of system default is 20, so set vm.dirty_ratio of virtual-host to 10.

RHEL 7: Virtualization Tuning and Optimization Guide: Chapter 4. tuned and tuned-adm:

Based on the throughput-performance profile, virtual-host also enables more aggressive writeback of dirty pages. This profile is the recommended profile for virtualization hosts, including both KVM and Red Hat Virtualization (RHV) hosts.

RHEL 8: Configuring and managing virtualization: Chapter 16. Optimizing virtual machine performance:

For RHEL 8 virtualization hosts, use the virtual-host profile. This enables more aggressive writeback of dirty memory pages, which benefits the host performance.

RHEL 9: Configuring and managing virtualization: Chapter 17. Optimizing virtual machine performance:

For RHEL 9 virtualization hosts, use the virtual-host profile. This enables more aggressive writeback of dirty memory pages, which benefits the host performance.

"This enables more aggressive writeback of dirty memory pages, which
benefits the host performance."

Signed-off-by: 谢致邦 (XIE Zhibang) <[email protected]>
@yarda
Copy link
Contributor

yarda commented Mar 9, 2023

Thanks for the contribution and sorry for the delay. Do you have some benchmark data supporting this change? It's apparent that this needs a fix, but it could be also fixed in the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants