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

Jump to bottom

TRIM SSD #105

Open

flx5 opened this issue Dec 29, 2023 · 0 comments

Owner

flx5 commented Dec 29, 2023

SSD write performance before trimming on /mnt/vm/ and nextcloud file system.

root@nas:/mnt/vm/libvirt# time dd if=/dev/zero of=tst.out bs=4M count=1024
1024+0 records in
1024+0 records out
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 95.8851 s, 44.8 MB/s

real	1m35.888s
user	0m0.010s
sys	0m3.301s

After calling fstrim:

root@nas:/mnt/vm/libvirt# time dd if=/dev/zero of=tst.out bs=4M count=1024
1024+0 records in
1024+0 records out
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 24.3756 s, 176 MB/s

real	0m24.379s
user	0m0.011s
sys	0m3.494s

Cronjob might be missing on the host: https://wiki.ubuntuusers.de/SSD/TRIM/#TRIM-mit-Festplattenverschluesselung
However every vm using lvm disks directly would also need to call trim (100 GB trimmed on nextcloud).

In my opinion the VMs aren't supposed to require knowledge of the underlying hardware. Need to find a solution.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment