From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756152AbXFXNA0 (ORCPT ); Sun, 24 Jun 2007 09:00:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754861AbXFXNAR (ORCPT ); Sun, 24 Jun 2007 09:00:17 -0400 Received: from mx.treblig.org ([80.68.94.177]:4846 "EHLO mx.treblig.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754755AbXFXNAQ (ORCPT ); Sun, 24 Jun 2007 09:00:16 -0400 Date: Sun, 24 Jun 2007 13:59:57 +0100 From: "Dr. David Alan Gilbert" To: Michael Tokarev Cc: Jeff Garzik , Carlo Wood , Tejun Heo , Manoj Kasichainula , linux-kernel@vger.kernel.org, IDE/ATA development list Subject: Re: SATA RAID5 speed drop of 100 MB/s Message-ID: <20070624125957.GA28067@gallifrey> References: <20070620224847.GA5488@alinoe.com> <4679B2DE.9090903@garzik.org> <20070622214859.GC6970@alinoe.com> <467CC5C5.6040201@garzik.org> <20070623125316.GB26672@alinoe.com> <467DA1F5.2060306@garzik.org> <467E5C5E.6000706@msgid.tls.msk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <467E5C5E.6000706@msgid.tls.msk.ru> X-Chocolate: 70 percent or better cocoa solids preferably X-Operating-System: Linux/2.6.20.3-bytemark-uml-2 (i686) X-Uptime: 13:53:15 up 51 days, 6:36, 1 user, load average: 0.31, 0.39, 0.42 User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Michael Tokarev (mjt@tls.msk.ru) wrote: > By the way, I did some testing of various drives, and NCQ/TCQ indeed > shows some difference -- with multiple I/O processes (like "server" > workload), IF NCQ/TCQ is implemented properly, especially in the > drive. > > For example, this is a good one: > > Single Seagate 74Gb SCSI drive (10KRPM) > > BlkSz Trd linRd rndRd linWr rndWr linR/W rndR/W > 1024k 1 83.1 36.0 55.8 34.6 28.2/27.6 20.3/19.4 > 2 45.2 44.1 36.4/ 9.9 > 4 48.1 47.6 40.7/ 7.1 > > The tests are direct-I/O over whole drive (/dev/sdX), with > either 1, 2, or 4 threads doing sequential or random reads > or writes in blocks of a given size. For the R/W tests, > we've 2, 4 or 8 threads running in total (1, 2 or 4 readers > and the same amount of writers). Numbers are MB/sec, as > totals (summary) for all threads. > > Especially interesting is the very last column - random R/W > in parallel. In almost all cases, more threads gives larger > total speed (I *guess* it's due to internal optimisations in > the drive -- with more threads the drive has more chances to > reorder commands to minimize seek time etc). > > The only thing I don't understand is why with larger I/O block > size we see write speed drop with multiple threads. My guess is that something is chopping them up into smaller writes. > And in contrast to the above, here's another test run, now > with Seagate SATA ST3250620AS ("desktop" class) 250GB > 7200RPM drive: > > BlkSz Trd linRd rndRd linWr rndWr linR/W rndR/W > 1024k 1 78.4 34.1 33.5 24.6 19.6/19.5 16.0/12.7 > 2 33.3 24.6 15.4/13.8 > 4 34.3 25.0 14.7/15.0 > > And second, so far I haven't seen a case where a drive > with NCQ/TCQ enabled works worse than without. I don't > want to say there aren't such drives/controllers, but > it just happen that I haven't seen any.) Yes you have - the random writes with large blocks and 2 or 4 threads is significantly better for your non-NCQ drive; and getting more significant as you add more threads - I'm curious what happens on 8 threads or more. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \ \ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex / \ _________________________|_____ http://www.treblig.org |_______/