Re: Buffer Requests Trace - Mailing list pgsql-hackers

From Lucas Lersch
Subject Re: Buffer Requests Trace
Date
Msg-id CAGR3jZBW3-=B-_PhbNv9i-pCeLj3gdo1+iZELW0Cr00Wr3fxzg@mail.gmail.com
Whole thread Raw
In response to Re: Buffer Requests Trace  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Buffer Requests Trace
Re: Buffer Requests Trace
List pgsql-hackers
So is it a possible normal behavior that running tpcc for 10min only access 50% of the database? Furthermore, is there a guideline of parameters for tpcc (# of warehouses, execution time, operations weight)?

On Wed, Oct 15, 2014 at 3:09 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
On 15 October 2014 13:44, Lucas Lersch <lucaslersch@gmail.com> wrote:

> I am recording the BufferDesc.tag.blockNum for the buffer along with the
> spcNode, dbNode, relNode, also present in the tag.

The TPC-C I/O is random, so if you run it for longer you should see a wider set.

Cacheing isn't possible as a way to improve txn rates.

Check that you're touching all tables.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



--
Lucas Lersch

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Buffer Requests Trace
Next
From: Andrew Dunstan
Date:
Subject: Re: narwhal and PGDLLIMPORT