pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Grega Bremec <gregab@p0f.net>
To: Given, Robert A <bgiven@bu.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgresql and uPortal
Date: Fri, 03 Mar 2006 14:31:32 +0100
Message-ID: <44084534.7070106@p0f.net> (raw)
In-Reply-To: <94A24C93CB808844ACB7444B3A188AB41A11B917@XMS.ad2.bu.edu>
References: <94A24C93CB808844ACB7444B3A188AB41A11B917@XMS.ad2.bu.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Given, Robert A wrote:
| We are beginning to implement uPortal on  Postgresql 7.4.8 on a
| z/Linux server. We are interested in obtaining information pertaining
| to any modification of the configuration parameters as distributed
| with the DBMS.
|
| Can anyone provide details on changes made such as:
|
| - adjustments in physical space allocation

What kind of storage are you using? Dedicated DASD or MDISKs, or perhaps
even SCSI? You may be able to achieve results ranging wildly on either
side of the scale, depending on your workload and storage scheme
deployed. Also, what kind of platform? LPAR or z/VM?

| - adjustments in virtual space allocation
| - shared buffers, cache sizes etc.
| - changes in database management parms

You will need to get a very good idea of what your average (database)
working set size is, because you're dealing with several layers of
indirection (IOCP cache, z/VM cache /if any/, z/Linux operating system
cache, page access frequencies) and it is extremely difficult to shoot
wild ducks and actually hit any in such an environment.

In general though, if you have a lot of guests on your machine, the rule
of thumb is, keep storage low, just a tiiiny bit higher than needed to
have the guest machine start paging, or even allow some (smaller) system
areas to be paged out, if it turns out they are seldomly used.

As for z/Linux parameters, PostgreSQL will ideally need page cache the
size of your working set.

| - changes in other system parms

Please specify more specific details on your current system environment.
You have not really given enough information to give any directly
related hints.

Regards,
- --
~    Grega Bremec
~    gregab at p0f dot net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFECEU0fu4IwuB3+XoRAziMAJ48Q2IAg/gsPUBFrvrg960//q8SqgCfdtc3
CAtgJfPZQe5ICR7/6qHL8jY=
=I3Kd
-----END PGP SIGNATURE-----



view thread (4+ messages)

Message-ID: <44084534.7070106@p0f.net>
Permalink:  ../44084534.7070106@p0f.net/
Also on:    postgresql.org/message-id/44084534.7070106@p0f.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: gregab@p0f.net, bgiven@bu.edu
  Subject: Re: Postgresql and uPortal
  In-Reply-To: <44084534.7070106@p0f.net>
  References: <94A24C93CB808844ACB7444B3A188AB41A11B917@XMS.ad2.bu.edu> <44084534.7070106@p0f.net>

* 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