All of lore.kernel.org
 help / color / mirror / Atom feed
* Clustered IO (was: Re: [patch][rfc][rft] vm throughput 2.4.2-ac4)
       [not found] <97j66o$7fej5$1@fido.engr.sgi.com>
@ 2001-02-28 19:14 ` Rajagopal Ananthanarayanan
  0 siblings, 0 replies; only message in thread
From: Rajagopal Ananthanarayanan @ 2001-02-28 19:14 UTC (permalink / raw)
  To: Rik van Riel, linux-kernel

Rik van Riel wrote:

> 
> Another solution would be to do some more explicit IO clustering and
> only flush _large_ clusters ... no need to invoke extra disk seeks
> just to free a single page, unless you only have single pages left.

Hi Rik,

Yes, clustering IO at the higher level can improve performance.
This improvement is on top of the excellent elevator changes that
Jens Axboe has done in 2.4.2. In XFS we are doing clustering
at writepage(). There are two paths:

	1. page_launder() -> writepage() -> cluster
		# this path under memory pressure.
	2. try_to_free_buffers() -> writepage() -> cluster
		# this path under background writing as in bdflush
		# but can also be used by sync() type operations that
		# work with buffers than pages.

Clustering by itself (in XFS) improves write performance by about 15-20%,
and we're seeing close to raw I/O performance. With clustering
the IO requests are pegged at 1024 sectors (512K bytes)
when performing large sequential writes ...


ananth.


--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2001-02-28 19:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <97j66o$7fej5$1@fido.engr.sgi.com>
2001-02-28 19:14 ` Clustered IO (was: Re: [patch][rfc][rft] vm throughput 2.4.2-ac4) Rajagopal Ananthanarayanan

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.