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

Evaluate performance tuning ideas #16

Open
GoogleCodeExporter opened this issue Aug 3, 2015 · 4 comments
Open

Evaluate performance tuning ideas #16

GoogleCodeExporter opened this issue Aug 3, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Although the long term goal is to move to new bits, we might also want to play 
around with the 
current build and see if we can tweak out some more performance. I don't know 
how much of the 
performance difference these changes[1] come from just disabling checksums, but 
it if is a long 
time until we can get mac-zfs caught up… well, maybe we can at least make a 
few people happy 
with some better performance.

[1] http://lists.macosforge.org/pipermail/zfs-discuss/2009-September/001855.html

Original issue reported on code.google.com by jason.richard.mcneil on 2 Nov 2009 at 7:24

@GoogleCodeExporter
Copy link
Author

Here's the nabble link, if/when the macosforge list gets removed:

http://n3.nabble.com/ZFS-performance-tuning-td21704.html#a21704

Note that the bug listed in here was part of 124, but here's the change:

hg log -r 0e96dd3b905a

Diff (against the hg) is attached. We may not be able to roll forward to this 
until later.

Original comment by alex.ble...@gmail.com on 2 Nov 2009 at 11:37

Attachments:

@GoogleCodeExporter
Copy link
Author

Don't forget tuning is evil.

http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide

Original comment by sammyomi...@gmail.com on 3 Nov 2009 at 5:39

@GoogleCodeExporter
Copy link
Author

I don't think it's going to be too long before we roll forwards, which will 
bring some of those enhancements. In 
any case, a lot of performance tuning is going to be load/machine/disk 
dependent. 

What will be really cool is to experiment with a separate ZIL device, which we 
don't have yet (but I think was 
added fairly soon after the 72 split).

By all means, let's discuss possibilities here, but as for code optimisations, 
it might be difficult to roll forward 
those in the future if we then pick up a good split point for ZFS.

Original comment by alex.ble...@gmail.com on 5 Nov 2009 at 9:49

@GoogleCodeExporter
Copy link
Author

I think the link now refers to

http://mac-os-x-zfs-discuss.19757.n3.nabble.com/ZFS-performance-tuning-td21704.h
tml

Original comment by alex.ble...@gmail.com on 6 Jan 2011 at 1:52

  • Changed state: Accepted

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

No branches or pull requests

1 participant