On Tue, Oct 21, 2008 at 6:27 PM, Brian K. White
Also, I doubt you have an application that can either produce or consume data at 180MB/sec or faster, so this is all just a benchmark war I assume.
Amazing leap. I didn't hear him say anything about his usage other than to use the word "server" in a sentence.
I would say the opposite, that disk i/o is the main bottle neck for most services these days and so, lacking specific details, if you had to assume anything, it's safer to assume that his application IS disk i/o bound than not.
Every one of my servers, being multi-user real time database driven application servers performing unholy numbers of small random access transactions to many files at once, can always use all the disk bandwidth that can possibly be provided.
With your servers, what does iostat show your MB/sec rate to be? I issue the command as "iostat -d 10". The blocks/second column is in sectors. 180MB/sec * 2,000 sectors/MB ==> 360,000 sectors/sec. If iostat is showing above 360,000 sectors/second with a real world app I will be very surprised. Much more likely you are limited by some other bottleneck than raw data throughput at that rate. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org