Skip to content

RavenDB-26218 Document read_ahead_kb tuning and the new storage config options#2504

Open
arekpalinski wants to merge 2 commits into
ravendb:mainfrom
arekpalinski:RavenDB-26218
Open

RavenDB-26218 Document read_ahead_kb tuning and the new storage config options#2504
arekpalinski wants to merge 2 commits into
ravendb:mainfrom
arekpalinski:RavenDB-26218

Conversation

@arekpalinski

Copy link
Copy Markdown
Member

Issue link

https://issues.hibernatingrhinos.com/issue/RavenDB-26218

Additional description

PR in RavenDB: ravendb/ravendb#22676

  • Add a block-device tuning section (read_ahead_kb, scheduler, rotational) to the system configuration recommendations, framed as opt-in for heavy random-access load.
  • Document Storage.ReadAheadKbAlertThresholdInKb and Storage.UseSequentialReadAheadHintForJournalRecovery in the storage configuration reference.
  • Drop the stale "Ubuntu 16.04" qualifier from the Linux heading.

Type of change

  • Content - docs
  • Content - cloud
  • Content - guides
  • Content - start pages/other
  • New docs feature (consider updating /templates or readme)
  • Bug fix
  • Optimization
  • Other

Changes in docs URLs

  • No changes in docs URLs
  • Articles are restructured, URLs will change, mapping is required (update /scripts/redirects.json file, set Documents Moved PR label)

Changes in UX/UI

  • No changes in UX/UI
  • Changes in UX/UI (include screenshots and description)

…g options

- Add a block-device tuning section (read_ahead_kb, scheduler, rotational) to the system configuration recommendations, framed as opt-in for heavy random-access load.
- Document Storage.ReadAheadKbAlertThresholdInKb and Storage.UseSequentialReadAheadHintForJournalRecovery in the storage configuration reference.
- Drop the stale "Ubuntu 16.04" qualifier from the Linux heading.

# Installation: System Configuration Recommendations

## Linux - Ubuntu 16.04

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🥹


Also check `rotational` and `scheduler`. They matter most on virtualized disks (Azure managed disks in particular), which are often misreported as `rotational` even when backed by SSD/NVMe, so the kernel picks HDD-oriented defaults. Bare-metal SSD/NVMe is usually detected correctly. For SSD/NVMe, `rotational=0` and `scheduler=none` are usually better.

Persist these across reboots with a udev rule:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

need to mention this applies the values to ALL disks here and users should check and apply the rule for the disks used by RavenDB.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Added the note in 6da742f

…ll users to scope it to the disks RavenDB actually uses.
@arekpalinski arekpalinski requested a review from ppekrol June 19, 2026 07:29
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.

3 participants