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

Add dm-cache documentation for XOSTOR #295

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

Conversation

Wescoeur
Copy link
Member

@Wescoeur Wescoeur commented Nov 6, 2024

Before submitting the pull request, you must agree with the following statements by checking both boxes with a 'x'.

  • "I accept that my contribution is placed under the CC BY-SA 2.0 license [1]."
  • "My contribution complies with the Developer Certificate of Origin [2]."

[1] https://creativecommons.org/licenses/by-sa/2.0/
[2] https://docs.xcp-ng.org/project/contributing/#developer-certificate-of-origin-dco

@Wescoeur Wescoeur requested a review from Nambrok November 6, 2024 21:30
docs/xostor/xostor.md Outdated Show resolved Hide resolved
docs/xostor/xostor.md Outdated Show resolved Hide resolved
linstor vg set-property xcp-sr-linstor_group_thin_device 0 Cache/OpMode <MODE>
```

By default `writethrough` mode is used. This mode is only useful to improve read performance.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure to understand the cache system: are reads already "cached" by design in LINSTOR? ie doesn't wait to read to another node but having the local disk speed for it. Last time I did a bench, this is what I had. So I am probably ignoring something obvious in there.

Copy link
Member Author

@Wescoeur Wescoeur Nov 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DRBD can use the Linux system's buffers. But by design you don't have a cache: the read requests can be sent to the local host currently used and/or on another machine to accelerate parallel requests.

The interest of dm-cache here is to use HDDs (or slow SSDs) on the DRBD level and a faster device like an NVME to cache the most read blocks.

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