X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 3687D9DC9D2 for ; Fri, 3 Mar 2006 09:30:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47958-07 for ; Fri, 3 Mar 2006 09:30:46 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id BB3BA9DC8E0 for ; Fri, 3 Mar 2006 09:30:40 -0400 (AST) Received: from p0f.net (p0f.net [193.77.154.190]) by svr4.postgresql.org (Postfix) with ESMTP id 10B1F5AF86F for ; Fri, 3 Mar 2006 13:30:39 +0000 (GMT) Received: from [10.10.190.53] ([193.77.165.58]) (authenticated bits=0) by p0f.net (8.13.3/8.13.3) with ESMTP id k23CsKau030320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Mar 2006 13:54:24 +0100 Message-ID: <44084534.7070106@p0f.net> Date: Fri, 03 Mar 2006 14:31:32 +0100 From: Grega Bremec Organization: P0F User-Agent: Mozilla Thunderbird 1.0 (X11/20041207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Given, Robert A" Cc: pgsql-admin@postgresql.org Subject: Re: Postgresql and uPortal References: <94A24C93CB808844ACB7444B3A188AB41A11B917@XMS.ad2.bu.edu> In-Reply-To: <94A24C93CB808844ACB7444B3A188AB41A11B917@XMS.ad2.bu.edu> X-Enigmail-Version: 0.93.0.0 OpenPGP: id=E077F97A Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.833 required=5 tests=[AWL=0.120, RCVD_IN_NJABL_DUL=1.713] X-Spam-Score: 1.833 X-Spam-Level: * X-Archive-Number: 200603/35 X-Sequence-Number: 20792 -----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-----