pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: testperf-general@pgfoundry.org, Jan Wieck <JanWieck@Yahoo.com>
Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ...
Date: Fri, 8 Oct 2004 16:31:41 -0700
Message-ID: <200410081631.41545.josh@agliodbs.com> (raw)
In-Reply-To: <21365.1097274088@sss.pgh.pa.us>
References: <200410081443.16109.josh@agliodbs.com>
	<21365.1097274088@sss.pgh.pa.us>

Tom,

> BTW, what is the actual size of the test database (disk footprint wise)
> and how much of that do you think is heavily accessed during the run?
> It's possible that the test conditions are such that adjusting
> shared_buffers isn't going to mean anything anyway.

The raw data is 32GB, but a lot of the activity is incremental, that is 
inserts and updates to recent inserts.    Still, according to Mark, most of 
the data does get queried in the course of filling orders.

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco



view thread (41+ messages)  latest in thread

Message-ID: <200410081631.41545.josh@agliodbs.com>
Permalink:  ../200410081631.41545.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200410081631.41545.josh@agliodbs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us, JanWieck@Yahoo.com
  Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ...
  In-Reply-To: <200410081631.41545.josh@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox