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

OpenZFS 7104 - Increase indirect block size #4800

Closed
wants to merge 1 commit into from

Conversation

sempervictus
Copy link
Contributor

Reviewed by: George Wilson [email protected]
Reviewed by: Paul Dagnelie [email protected]
Ported by: Boris Lukashev [email protected]

The current default indirect block size is 16KB. We can improve
performance by increasing it to 128KB. This is especially helpful for
any workload that needs to read most of the metadata, e.g.
scrub/resilver, file deletion, filesystem deletion, and zfs send.

We also need to fix a few space estimation errors to make the tests
pass.

Upstream bug: DLPX-35881

OpenZFS Issue: openzfs/openzfs#132

Testing:
Passed ztest atop internal test stack (ABD and the like) on Ubuntu 14.04 with kernel 4.6.3

Reviewed by: George Wilson <[email protected]>
Reviewed by: Paul Dagnelie <[email protected]>
Ported by: Boris Lukashev <[email protected]>

The current default indirect block size is 16KB. We can improve
performance by increasing it to 128KB.  This is especially helpful for
any workload that needs to read most of the metadata, e.g.
scrub/resilver, file deletion, filesystem deletion, and zfs send.

We also need to fix a few space estimation errors to make the tests
pass.

Upstream bug: DLPX-35881

OpenZFS Issue: openzfs/openzfs#132
@sempervictus
Copy link
Contributor Author

Seems all the failures are on ziltest, but other than a timeout being caused by... something... i'm not getting much from the output.
I'll pull the test script into one of our testbeds and see how it behaves.

@behlendorf
Copy link
Contributor

Replaced by #4989

@behlendorf behlendorf closed this Aug 18, 2016
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