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

record size for database dataset: 16K or 32K? #207

Open
rm76 opened this issue Aug 28, 2023 · 2 comments
Open

record size for database dataset: 16K or 32K? #207

rm76 opened this issue Aug 28, 2023 · 2 comments

Comments

@rm76
Copy link

rm76 commented Aug 28, 2023

When setting up a dataset for the database and setting 16K as record size, I get this warning:
WARNING: Based on the pool topology, 32K is the minimum recommended record size. Choosing a smaller size can reduce system performance.
Should I go for 16K or 32K?

@DD8372812
Copy link

I recently reinstalled Nextcloud using this script and asked myself the same question. I have selected 16K.

After the successful installation Nextcloud Web GUI is very sluggish. Could this have something to do with the wrong size?

@slothish
Copy link

slothish commented Apr 2, 2024

You want a record size of 16k

https://kitcharoenp.github.io/mysql/zfs/mariadb/2021/10/18/zfs-tunning-optimization.html

To get the best performance you should put the database on a dedicated ssd pool

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

No branches or pull requests

3 participants