Date: Thu, 29 Mar 2007 11:29:17 +0200 From: =?ISO-8859-1?B?U3phYvMgUOl0ZXI=?= <matyee@mail.alba.hu> To: <freebsd-geom@freebsd.org> Subject: Re: raid3 is slow Message-ID: <005301c771e4$bb0a3900$6502a8c0@peteruj> References: <003401c7712a$f71ebb60$6502a8c0@peteruj><eudlg8$pm4$1@sea.gmane.org> <005c01c77134$28e0fce0$6502a8c0@peteruj> <86zm5xph7o.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- > From: "Dag-Erling "Smřrgrav"" <des@des.no> > > Szabó Péter <matyee@mail.alba.hu> writes: > > # graid3 list > > > > Geom name: nmivol > > State: DEGRADED > > First of all, your array is degraded. The graid3 output shows only > four components. Unless the missing fifth component happens to be the > parity disk, geom_raid3 will have to reconstruct your data on the fly. > > Second, you say nothing about which spindles the components are on and > how those spindles are attached to the system. If some of those > components are on the same spindle, or if some of those spindles are > on the same ATA channel, performance will suffer considerably. Array problem solved. But my problem is not the low read/write performance, my problem is the high load. I start a single bittorrent download to the encoded raid3 partition with 2.5MB/s speed, and the load is 2.5. Matyee
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005301c771e4$bb0a3900$6502a8c0>