Re: Bug: Buffer cache is not scan resistant - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Bug: Buffer cache is not scan resistant
Date
Msg-id 87slckdmqg.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: Bug: Buffer cache is not scan resistant  ("Luke Lonergan" <LLonergan@greenplum.com>)
List pgsql-hackers
"Luke Lonergan" <LLonergan@greenplum.com> writes:

> The evidence seems to clearly indicate reduced memory writing due to an
> L2 related effect.  

You might try using valgrind's cachegrind tool which I understand can actually
emulate various processors' cache to show how efficiently code uses it. I
haven't done much with it though so I don't know how applicable it would be to
a large-scale effect like this. 

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: "Luke Lonergan"
Date:
Subject: Re: Bug: Buffer cache is not scan resistant
Next
From: ITAGAKI Takahiro
Date:
Subject: Aggressive freezing in lazy-vacuum