Re: 2.6.0-test9 - poor swap performance on low end machines

From: Roger Luethi (rl_at_hellgate.ch)
Date: 12/09/03

  • Next message: Paul Jakma: "Re: Device-mapper submission for 2.4"
    Date: 	Tue, 9 Dec 2003 17:31:49 +0100
    To: Rik van Riel <riel@redhat.com>
    
    

    On Tue, 09 Dec 2003 11:04:49 -0500, Rik van Riel wrote:
    > > The classic strategies based on these criteria work for transaction and
    > > batch systems. They are all but useless, though, for a workstation and
    > > even most modern servers, due to assumptions that are incorrect today
    > > (remember all the degrees of freedom a scheduler had 30 years ago)
    > > and additional factors that only became crucial in the past few decades
    > > (latency again).
    >
    > Don't forget that computers have gotten a lot slower
    > over the years ;)
    >
    > Swapping out a 64kB process to a disk that does 180kB/s
    > is a lot faster than swapping out a 100MB process to a
    > disk that does 50MB/s ...
    >
    > Once you figure in seek times, the picture looks even
    > worse.

    Exactly -- I did mention the growing access time gap between RAM and
    disks in an earlier message. Yes, there are quite a few developments in
    hardware and in the way we use computers (interactive, Client/Server,
    dedicated machines, etc.) that made thrashing pretty much unsolvable
    at an OS level. Fortunately, fixing it in hardware by adding RAM works
    for most.

    What we _can_ do in software, though, is prevent thrashing as long as
    possible. Comparing 2.4 and 2.6 shows that a kernel can still make a
    significant difference with smart pageout algorithms, I/O scheduling etc.
    But you won't get much help with that from ancient papers.

    Roger
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Paul Jakma: "Re: Device-mapper submission for 2.4"

    Relevant Pages

    • Re: lockups with 2.4.2x
      ... there is a lot of hardware in this box. ... Your hangs may be related to an updatedb or slocate ... You may also have a defect in your RAM. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: log-buf-len dynamic
      ... Larry, I think you remember the good old days of SunOS, when 16MB of RAM ... and people expected less of their hardware. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test9 - poor swap performance on low end machines
      ... because variance in thrashing benchmarks is pretty bad). ... Problem is, ten or twenty kernel releases later, you can't easily ... * We don't want to kill a process with direct hardware access. ... several, independant regressions. ...
      (Linux-Kernel)
    • Re: Problems with IE after clean Install of Win XP & SP2
      ... I think hardware check may be my next step. ... The system is a Dell Dimension 8600, 232 GB hard drive, 1GB ram. ... Memory performace seems fine - Commit figures (Total=315 MG and Peak ... I* have only loaded Avast antivirus and MS Office 2003. ...
      (microsoft.public.windowsxp.general)
    • Re: When people say Leopard is problematic...
      ... Why am I removing Kingston Brand ECC registered SDRAM while it passes the every RAM test available on Mac scene? ... Therotically, even if it is broken, it will keep working, that is why we pay extra price for ECC and ECC supporting machines/mainboards. ... is why we use high end Apple workstations. ... So, "NO", it is NOT a hardware issue, ...
      (comp.sys.mac.system)