public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Pielmeier <daniel.pielmeier@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Performance problem at writing big files and Multitasking
Date: Wed, 07 Feb 2007 22:39:20 +0100	[thread overview]
Message-ID: <45CA4708.9010307@googlemail.com> (raw)
In-Reply-To: <45C9F7A1.10806@comcast.net>

> The hdparm optimizations, the CFQ scheduler and maybe low latency
> desktop in the kernel are the best way to make your desktop useable
> under heavy disk usage.These are my hdparm settings:
> 
> /dev/hda:
>  multcount    = 16 (on)
>  IO_support   =  1 (32-bit)
>  unmaskirq    =  1 (on)
>  using_dma    =  1 (on)
>  keepsettings =  0 (off)
>  readonly     =  0 (off)
>  readahead    = 256 (on)
>  geometry     = 26310/16/63, sectors = 26520480, start = 0
> 
> cat /sys/block/hda/queue/scheduler
> noop [cfq]
> 
> Linux c-68-85-77-239 2.6.20-gentoo #4 PREEMPT Tue Feb 6 17:03:56 EST
> 2007 i686 AMD Athlon(tm) XP 2000+ AuthenticAMD GNU/Linux

Now  i am in front of my PC. I already use the cfq scheduler and have
low latency desktop enabled. I looked at the output of hdparm -I
/dev/sda and all seems to be ok by default.

> And check you have HZ set to 1000.
> 
> $ grep HZ /usr/src/linux/.config
> # CONFIG_HZ_100 is not set
> # CONFIG_HZ_250 is not set
> CONFIG_HZ_1000=y
> CONFIG_HZ=1000

Thanks i will check if this helps, i have just set 250 HZ for timer
frequency.

> Could your problem be similar to this:
> 
>    http://marc.theaimsgroup.com/?l=gentoo-user&m=114252338111258&w=2
> 
> 
> Tom

Maybe, today the gentoo-sources-2.6.19-r5 become stable so i will try
the new kernel. I am also waiting for kernel 2.6.20 as it has a setting
for the core 2 duo in processor settings. Maybe i try the testing
version of it.
Also the new gcc compilers will support the core 2 duo directly, but i
think it will take some time till 4.2 or even 4.3 will become stable.

I show up here again and tell you if something improves the performance
of my system.

Regards

Daniel
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-02-07 21:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7LFgI-6qK-17@gated-at.bofh.it>
     [not found] ` <7LFqt-6Eo-27@gated-at.bofh.it>
     [not found]   ` <7LUIK-4Qn-3@gated-at.bofh.it>
2007-02-07 16:00     ` [gentoo-user] Performance problem at writing big files and Multitasking Mike
2007-02-07 16:39       ` Daniel Pielmeier
2007-02-07 18:08       ` Benno Schulenberg
2007-02-07 21:39       ` Daniel Pielmeier [this message]
2007-02-10 11:49         ` Daniel Pielmeier
2007-02-26 16:28           ` Matthias Bethke
2007-02-27  7:49             ` Kellystewart00
2007-02-06 20:31 Daniel Pielmeier
2007-02-06 20:50 ` Michael Schreckenbauer
2007-02-06 21:25   ` Daniel Pielmeier
2007-02-06 21:16 ` Etaoin Shrdlu
2007-02-06 21:28   ` Daniel Pielmeier
2007-02-08 10:42     ` Frédéric Grosshans
2007-02-08 18:34       ` Daniel Pielmeier
2007-02-08 19:12         ` Etaoin Shrdlu
2007-02-08 23:14       ` Iain Buchanan
2007-02-06 22:25   ` Daniel Pielmeier
2007-02-07 12:59   ` Daniel Pielmeier
2007-02-07 19:16     ` Tom Naujokas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45CA4708.9010307@googlemail.com \
    --to=daniel.pielmeier@googlemail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox