Mailinglist Archive: opensuse-factory (422 mails)
| < Previous | Next > |
Re: [opensuse-factory] [boottime] The effect of preload
- From: Hans Petter Jansson <hpj@xxxxxxxxxx>
- Date: Mon, 26 Jan 2009 12:45:51 +0100
- Message-id: <1232970351.3609.64.camel@xxxxxxxxxxxxxxx>
On Mon, 2009-01-26 at 09:17 +0000, Michael Meeks wrote:
By the way, I guess this isn't as effective if you only have one or two
processes blocking on reads - won't they have only one outstanding
request each at any given time?
Readahead notwithstanding, has anyone tried to make apps that need to
read lots of small files, read each in a separate thread simultaneously
to maximize the elevator benefits (thinking especially about GConf here
- AFAIK it's currently serializing concurrent requests)?
Relatedly, I'm packaging sreadahead in devel:playground:fastboot now -
the kernel-source package in there has the requisite kernel patch.
--
Hans Petter
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
* do you take the moblin route:
+ of running preload asynchronously at the lowest
I/O priority
+ of growing /sys/proc/sda/queue/nr_requests to
1024+ [ supposedly so the fairness code works ;-)
By the way, I guess this isn't as effective if you only have one or two
processes blocking on reads - won't they have only one outstanding
request each at any given time?
Readahead notwithstanding, has anyone tried to make apps that need to
read lots of small files, read each in a separate thread simultaneously
to maximize the elevator benefits (thinking especially about GConf here
- AFAIK it's currently serializing concurrent requests)?
Relatedly, I'm packaging sreadahead in devel:playground:fastboot now -
the kernel-source package in there has the requisite kernel patch.
--
Hans Petter
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |