Skip to content

DOC-1324 SSD backed persistent volumes typo #1112

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.

Sign up for GitHub

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

Merged
micheleRP merged 4 commits into from
May 8, 2025
Merged

DOC-1324 SSD backed persistent volumes typo #1112

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8cd1127
DOC-1324 SSD backed persistent volumes typo
micheleRP May 6, 2025
cd769ad
remove $ from apt command
micheleRP May 6, 2025
46e0b38
minor edit
micheleRP May 6, 2025
c40d616
incorporate feedback
micheleRP May 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions modules/deploy/pages/deployment-option/self-hosted/manual/sizing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ Redpanda is basically a distributed transaction log with well-understood access

Your best storage solution for your workload depends on your performance and data retention requirements.

If high throughput and low latency is most important, then use locally attached NVMe SSD disks. This is also a good option in the cloud. Just remember that in the cloud, local disks are ephemeral, so data is wiped when an instance is restarted. An alternative in the cloud is to use SSD-backed object storage to persist data between instance restarts. Most cloud providers have options for guaranteeing throughput and provisioned IOPS performance of network-attached storage, although network-attached storage almost always exhibits slightly higher tail latencies than direct-attached storage.
If high throughput and low latency is most important, then use locally attached NVMe SSD disks. This is also a good option in the cloud. Just remember that in the cloud, local disks are ephemeral, so data is wiped when an instance is restarted. An alternative in the cloud is to use SSD-backed persistent volumes to retain data between instance restarts. Most cloud providers have options for guaranteeing throughput and provisioned IOPS performance of network-attached storage, although network-attached storage almost always exhibits slightly higher tail latencies than direct-attached storage.
Copy link
Copy Markdown
Member

@travisdowns travisdowns May 7, 2025

Choose a reason for hiding this comment

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

When we say:

... is to use SSD-backed persistent volumes to retain ...
and
... provisioned IOPS performance of network-attached storage, although network-attached ...

we are talking about the same thing using two different terms "persistent" and "network-attached". I think we should use the same term "network-attached" in both places (and sorry, persistent was my suggestion).

Copy link
Copy Markdown
Contributor Author

@micheleRP micheleRP May 7, 2025

Choose a reason for hiding this comment

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

fixed


For example, AWS io2 volumes offer up to 64,000 IOPS and 1,000 MB/sec throughput with single-digit millisecond latency. This is an expensive option, so if you can trade performance for cost, then AWS gp3 volumes are a good alternative. GCP has comparable options with high-end Extreme persistent disks and the lesser SSD persistent disks. Likewise, Azure has Ultra, Premium, and Standard persistent disk options for choosing the right balance of performance versus cost.

Expand All @@ -87,9 +87,9 @@ NOTE: Ensure that the fio job runs against the chosen block device. By default,

[,bash]
----
$ sudo apt -y update; sudo apt -y install fio
$ cd /var/lib/redpanda/data
$ sudo cat > fio-seq-write.job << EOF
sudo apt -y update; sudo apt -y install fio
cd /var/lib/redpanda/data
sudo cat > fio-seq-write.job << EOF
Copy link
Copy Markdown
Member

@travisdowns travisdowns May 7, 2025

Choose a reason for hiding this comment

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

I was testing this and it actually does not work because the redirect > happen with the current user not root.

This works:

sudo tee fio-seq-write.job >/dev/null << EOF

Copy link
Copy Markdown
Contributor Author

@micheleRP micheleRP May 7, 2025

Choose a reason for hiding this comment

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

fixed: can you please re-review @travisdowns?

[global]
name=fio-seq-write
filename=fio-seq-write
Expand All @@ -105,7 +105,7 @@ size=10G
ioengine=libaio
iodepth=16
EOF
$ sudo fio fio-seq-write.job
sudo fio fio-seq-write.job
Copy link
Copy Markdown
Member

@travisdowns travisdowns May 7, 2025

Choose a reason for hiding this comment

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

Looks good but I'm also wondering if we do this elsewhere in our docs where we have shell code snippets?

Copy link
Copy Markdown
Contributor Author

@micheleRP micheleRP May 7, 2025

Choose a reason for hiding this comment

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

I ran a search and I think the rest are fine; e.g., see here or here.

----

Key performance metrics:
Expand Down