Swapping in 2.6.10 and 2.6.11.11 on a desktop system

From: Alexander Gretencord (arutha_at_gmx.de)
Date: 06/14/05

  • Next message: Jon Smirl: "Re: Input sysbsystema and hotplug"
    To: linux-kernel@vger.kernel.org
    Date:	Tue, 14 Jun 2005 16:53:30 +0200
    
    

    Hi,

    [1] With swappiness = 60 I either get swap hell (2.6.10) or the oom killer
    kicks in (2.6.11.11)

    [2] I upgraded to 2.6.11.11 from 2.6.8.1 yesterday and tried to compile
    something. After some time I come back and the compile has aborted because
    the oom killer killed the compiler process. There is no additional use of
    swap space (although some applications that were also running could have been
    swapped out). There was a similar bugreport with this behaviour some time ago
    for 2.6.11.8 but that one included a swappiness value of 0, i got 60.

    Then I tried 2.6.10. The oom bugs were gone, the compile finished over night.
    About an hour ago I started a very RAM consuming application and at 2/3 RAM
    usage I get swap hell. The system constantly swaps, yet ram usage _and_ swap
    usage stay about the same. Even setting swappiness to 0 from an ssh login
    (switching to a console does not work) did not help, only killing the
    consuming application.

    I also applied the ck hard-swappiness Patch to my 2.6.10 and tested a bit
    further. Depending on the swappiness I get hellish swapping behaviour at
    different levels of RAM usage and even managed to get the oom killer to step
    in (at swappiness=20). I had about 250MB of RAM used and boom -> oom killer
    shoots down some bigger java processes. At swappiness=80 I get massive
    swapping with 250MB of RAM usage. When reaching that level, the fs cache goes
    up to 300MB while the applications that need the ram are left with about 120
    megs. Rest was buffers.

    I'm really out of ideas. 2.6.8.1 with swappiness=0 is by far the best I've
    managed to get by now. With that I can use my system until RAM and swap are
    completely full. No swap hell and no oom killer yet. Maybe I just have to
    search the lkml a bit more to find something usable. If someone else already
    has, please tell me (and tell me why it's not in the mainline kernel
    already :))

    I have 512MB of RAM and another 512MB of swap.

    Please cc me in replies as I'm not on the list.

    Alex
    -
    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: Jon Smirl: "Re: Input sysbsystema and hotplug"

    Relevant Pages

    • Re: 2.6.0-test9 - poor swap performance on low end machines
      ... >> Well I was considering adding the swap pressure to this algorithm but I ... It wont be as aggressive as setting the swappiness ... > The test compile started in a similar way to the compile when using your ... detriment of other tasks that are on the runqueue and still need ram. ...
      (Linux-Kernel)
    • 2.6.0-test9 - poor swap performance on low end machines
      ... I have been testing the 2.6.0-test9 kernel on a couple of desktop machines. ... On the first, a 1.8GHz Pentium 4 uniprocessor with 512MHz of RAM, it seems to ... perform fine, and on various compilation tests, compile times for the test ... Nothing I use it for knocks it substantially into swap. ...
      (Linux-Kernel)
    • Re: excessive swap-in time
      ... Trying to do it all with RAM is just inefficient. ... I find that does not work well when the swapping is caused by excessive I/O ... Or you could have 5 TB of swap space. ...
      (comp.os.linux.development.system)
    • SLUB 0:1 SLAB (OOM during massive parallel kernel builds)
      ... 2G of RAM, 1G of swap partition. ... DMA per-cpu: ... kill process 25286 score 188662 or a child ...
      (Linux-Kernel)
    • fork failed cannot allocate memory
      ... I have a Dell 2650, dual Xeon box, 2GB RAM, 6GB swap with PERC Hardware ... feeding the perl processes). ... Every week or two the box will stop allowing new netcool client ...
      (RedHat)