On Sun, 2007-12-23 at 20:11 -0500, Rik van Riel wrote:
> On Mon, 24 Dec 2007 04:29:36 +0530
> Balbir Singh <[EMAIL PROTECTED]> wrote:
> > Rik van Riel wrote:
>
> > > In the real world, users with large JVMs on their servers, which
> > > sometimes go a little into swap, can trigger this system. A
On Mon, 24 Dec 2007 04:29:36 +0530
Balbir Singh <[EMAIL PROTECTED]> wrote:
> Rik van Riel wrote:
> > In the real world, users with large JVMs on their servers, which
> > sometimes go a little into swap, can trigger this system. All of
> > the CPUs end up scanning the active list, and all pages ha
Rik van Riel wrote:
> On Sun, 23 Dec 2007 01:57:32 +0530
> Balbir Singh <[EMAIL PROTECTED]> wrote:
>> Rik van Riel wrote:
>>> On large memory systems, the VM can spend way too much time scanning
>>> through pages that it cannot (or should not) evict from memory. Not
>>> only does it use up CPU time
On Sun, 23 Dec 2007 01:57:32 +0530
Balbir Singh <[EMAIL PROTECTED]> wrote:
> Rik van Riel wrote:
> > On large memory systems, the VM can spend way too much time scanning
> > through pages that it cannot (or should not) evict from memory. Not
> > only does it use up CPU time, but it also provokes lo
Rik van Riel wrote:
> On large memory systems, the VM can spend way too much time scanning
> through pages that it cannot (or should not) evict from memory. Not
> only does it use up CPU time, but it also provokes lock contention
> and can leave large systems under memory presure in a catatonic sta
On large memory systems, the VM can spend way too much time scanning
through pages that it cannot (or should not) evict from memory. Not
only does it use up CPU time, but it also provokes lock contention
and can leave large systems under memory presure in a catatonic state.
This patch series impro
6 matches
Mail list logo
