Date: Sun, 3 Feb 2008 22:38:28 +0000 From: Chris <chrcoluk@gmail.com> To: "Michael Butler" <imb@protected-networks.net> Cc: Adam McDougall <mcdouga9@egr.msu.edu>, freebsd-stable@freebsd.org, Ivan Voras <ivoras@freebsd.org> Subject: Re: gjournal panic 7.0-RC1 Message-ID: <3aaaa3a0802031438u112fe5damc48adc286f308252@mail.gmail.com> In-Reply-To: <47A63610.4070608@protected-networks.net> References: <3aaaa3a0802030751w69ce59a9oeb869e3d87d92616@mail.gmail.com> <fo58j1$7hq$1@ger.gmane.org> <47A62B00.1060403@egr.msu.edu> <3aaaa3a0802031318y2e3fd33en8071c82172ab9ecf@mail.gmail.com> <47A63610.4070608@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> If I understood this thread correctly, the impression of poor > performance is based on a configuration where both the journal and the > data are on the same physical drive. Intuitively, this will likely > penalize any transaction on the volume, read or write, since you're > asking the drive to not only accumulate a queue of information to the > journal in one region of the disk but also to flush that data in "idle > time" to a region in the data space on that same disk at a significant > seek-length away. > > I would think that journaling on one drive and storing the resultant > data-set on another would improve performance enormously (reduced > seek-lengths) and more so if they were 1) high-rpm drives (less > rotational latency) and 2) on different buses (no bus/controller > contention), > > Michael > Yes I have suspected this, there is 2 physical drives in the machine so this would be possible, if its possible to swap the journals round so they journaling for each other I will give it a go tommorow. They both sata 300 drives. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3aaaa3a0802031438u112fe5damc48adc286f308252>