What I've been trying to do is squeeze some more write performance out of my system. (Dual Pentium Xeon processors, 1GB ram, software RAID, 2.4.20 kernel patched with XFS 1.3.1) I've ended up fiddli
hi there. Good stuff. Can you describe your workload there a bit more? Do you have multiple writers to the same file (from different NFS clients?)? Readers too? thanks. By "cleanup" I guess you mean
What I've been trying to do is squeeze some more write performance out of my system. (Dual Pentium Xeon processors, 1GB ram, software RAID, 2.4.20 kernel patched with XFS 1.3.1) I've ended up fiddli
Thanks Steve. After an audit, this seems to be valid for both 2.4 and 2.6. Mmmm? seems to me that i_sem is also held for nfs commit, both in 2.4 and 2.6 (nfsd_commit -> nfsd_sync -> down(i_sem) -> nf
Nathan Scott wrote: On Tue, Feb 24, 2004 at 12:20:22PM -0500, Alex Wun wrote: Hi. hi there. What I've been trying to do is squeeze some more write performance out of my system. Good stuff. I've ended
Nathan Scott wrote: I think its always valid to do this (after auditing the callers), but doesn't seem to do "general speedup" - the "usual suspects" benchmarks don't show any improvements anyway. Al
Sorry that I haven't gotten back to you in response to your question about the workload. Prior to your suggestion I had only tested a single application running on a single client over synchronous NF