Richard Elling - PAE wrote:
Torrey McMahon wrote:
Robert Milkowski wrote:
Hello Torrey,
Friday, November 10, 2006, 11:31:31 PM, you wrote:
[SNIP]
Tunable in a form of pool property, with default 100%.
On the other hand maybe simple algorithm Veritas has used is good
enough - simple delay between scrubing/resilvering some data.
I think a not-to-convoluted algorithm as people have suggested would
be ideal and then let people override it as necessary. I would think
a 100% default might be a call generator but I'm up for debate. ("Hey
my array just went crazy. All the lights are blinking but my
application isn't doing any I/O. What gives?")
I'll argue that *any* random % is bogus. What you really want to
do is prioritize activity where resources are constrained. From a RAS
perspective, idle systems are the devil's playground :-). ZFS already
does prioritize I/O that it knows about. Prioritizing on CPU might have
some merit, but to integrate into Solaris' resource management system
might bring some added system admin complexity which is unwanted.
I agree but the problem as I see it as that nothing has a overview of
the entire environment. ZFS knows what I/O is coming in and what its
sending out but that's it. Even if we had an easy to use resource
management framework across all the Sun applications and devices we'd
still run into non-Sun bits that place demands on shared components like
networking, san, arrays, etc. Anything that can be auto-tuned is great
but I'm afraid we're still going to need manual tuning in some cases.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
