mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
Cc: Jan Knutar <jk-lkml@sci.fi>,
	linux-kernel@vger.kernel.org,
	Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: swap prefetching merge plans
Date: Fri, 24 Mar 2006 09:16:07 +0100	[thread overview]
Message-ID: <4423AAC7.2050007@aitel.hist.no> (raw)
In-Reply-To: <200603231450.02479.volker.armin.hemmann@tu-clausthal.de>

Hemmann, Volker Armin wrote:

>On Thursday 23 March 2006 12:47, you wrote:
>  
>
>>On Thursday 23 March 2006 10:26, Nick Piggin wrote:
>>    
>>
>>>Hemmann, Volker Armin wrote:
>>>      
>>>
>>>>Hi,
>>>>
>>>>I am just a user, but I would love to see this feature.
>>>>
>>>>After compiling stuff, I have usually some kb in swap (300kb, 360 kb),
>>>>and lots of free ram. But even this few kb make my KDE desktop extremly
>>>>sluggish. It feels, like every byte is fetched individually and always
>>>>the wrong stuff ends in swap.
>>>>        
>>>>
>>>I'm almost positive this wouldn't be the cause of your problems (even a
>>>slow disk could read all these blocks in, randomly, in under 2 seconds,
>>>assuming they're spread from one end of the platters to the other).
>>>      
>>>
>>Maybe he meant 300 megabytes.
>>    
>>
>
>no, I meant kilobytes.
>
>And swapoff really helps.
>
>Some moments of disk activity, and bang, computer is as fast as always again.
>
>But having stuff in swap? konqueror is slow, kmail is slow, opening a konsole 
>session, slow. Everything crawls with lots of disk access. 
>
>next time the computer is slow, I could gather some data - if you tell me, 
>what is interessting for you, I'll save it.
>  
>
Strange indeed.  300k in swap is nothing - I often enough
have 50M in swap without a slowdown - but then, I don't
run kde. 

Be aware that the 300k in swap doesn't account for all that
is removed from memory.  Linux don't put executable code
in swap - such stuff is simply dropped because it can
be reloaded from the executable files anytime.
I don't think swapoff+swapon helps with that though.

Helge Hafting


  reply	other threads:[~2006-03-24  8:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  7:56 Hemmann, Volker Armin
2006-03-23  8:26 ` swap " Nick Piggin
2006-03-23 11:47   ` Jan Knutar
2006-03-23 13:50     ` Hemmann, Volker Armin
2006-03-24  8:16       ` Helge Hafting [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-23  4:53 -mm " Andrew Morton
2006-03-23  7:04 ` swap prefetching " Con Kolivas
2006-03-23 11:19   ` Jesper Juhl
2006-03-23 13:58   ` Francesco Biscani
2006-03-23 15:37     ` James Rayner
2006-03-23 18:35   ` Mattia Dongili
2006-03-23 18:40   ` Rafael J. Wysocki
2006-03-25 14:37   ` Jan Engelhardt
2006-03-25 15:24     ` Nick Piggin
2006-03-25 23:44       ` Con Kolivas
2006-03-26  5:54         ` Mike Galbraith
2006-03-26  8:08           ` Con Kolivas
2006-03-26  7:42             ` Mike Galbraith
2006-03-26  9:34               ` Con Kolivas
2006-03-26  9:20         ` Jan Engelhardt

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=4423AAC7.2050007@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=jk-lkml@sci.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=volker.armin.hemmann@tu-clausthal.de \
    /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

Powered by JetHome