X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id AE70BD1B4F1 for ; Mon, 6 Oct 2003 07:57:06 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 10749-03 for ; Mon, 6 Oct 2003 04:56:19 -0300 (ADT) Received: from ucsns.ucs.co.za (ucs.co.za [196.23.43.2]) by svr1.postgresql.org (Postfix) with ESMTP id 6704CD1B4E3 for ; Mon, 6 Oct 2003 04:56:14 -0300 (ADT) Received: from ucspost.ucs.co.za (mailgw1.ucs.co.za [196.23.43.253]) by ucsns.ucs.co.za (Postfix) with ESMTP id E1B7F2BDEC; Mon, 6 Oct 2003 09:56:00 +0200 (SAST) Received: from jhb.ucs.co.za (jhb.ucs.co.za [172.31.1.3]) by ucspost.ucs.co.za (Postfix) with ESMTP id EF8E9D9E78; Mon, 6 Oct 2003 09:56:00 +0200 (SAST) Received: from svb.ucs.co.za (svb.ucs.co.za [172.31.1.148]) by jhb.ucs.co.za (Postfix) with SMTP id 4CD4F973EA; Mon, 6 Oct 2003 09:56:01 +0200 (SAST) Date: Mon, 6 Oct 2003 09:55:51 +0200 From: Stef To: Josh Berkus Cc: pgsql-performance@postgresql.org Subject: Re: Postgres low end processing. Message-Id: <20031006095551.1d7bfeb8.svb@ucs.co.za> In-Reply-To: <200310031108.49002.josh@agliodbs.com> References: <20031003163040.3641f39a.svb@ucs.co.za> <200310031108.49002.josh@agliodbs.com> X-Mailer: Sylpheed version 0.9.5claws28 (GTK+ 1.2.10; i386-pc-linux-gnu) User-Agent: sillypheed-claws (anti-aliased) X-Face: LV^-*d3kQlL,6{Y:X)M~tuL#y!p.kO_Qbc!xxqhZC4s}Y]L0g)z^aiLsQGY34d|}Xp:HNm)MRsc?^?ZQ}smznF&jx|w@,a**K&QL.Dc~2~M5V`zb>hExCJDB[[o=M)e"; k-n[7tz2TY7+; *_xX's(5cUEtdw*yG-OmKm}6($zpUz8S`Nz@w X-Operating-System: sid X-X-X: _-^-_ Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Mon__6_Oct_2003_09_55_52_+0200_um.cP=ST1Zj13T9n" X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/169 X-Sequence-Number: 3917 --Signature=_Mon__6_Oct_2003_09_55_52_+0200_um.cP=ST1Zj13T9n Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Thanks for the replies, On Fri, 3 Oct 2003 11:08:48 -0700 Josh Berkus wrote: => 1. Make sure that the WAL files (pg_xlog) are on a seperate disk from the => database files, either through mounting or symlinking. I'm not sure I understand how this helps? => 2. Tweak the .conf file for low vacuum_mem (1024?), but vacuum very => frequently, like every 1-5 minutes. Spend some time tuning your => fsm_max_pages to the ideal level so that you're not allocating any extra => memory to the FSM. => => 3. If your concern is *average* CPU/RAM consumption, and not peak load => activity, increase wal_files and checkpoint_segments to do more efficient => batch processing of pending updates as the cost of some disk space. If peak => load activity is a problem, don't do this. => => 4. Tune all of your queries carefully to avoid anything requiring a => RAM-intensive merge join or CPU-eating calculated expression hash join, or => similar computation-or-RAM-intensive operations. Thanks, I'll try some of these, and post the results. The actual machines seem to be Pentium I machines, with 32M RAM. I've gathered that it is theoretically possible, so no to go try it. Regards Stef --Signature=_Mon__6_Oct_2003_09_55_52_+0200_um.cP=ST1Zj13T9n Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/gSARgDYs3UkRjZkRAts1AKChqytWZyhIRO3Qv9FkkJq021XtzgCfS5pq k3NfOBjojrci3nmE0lnOTFw= =bKRr -----END PGP SIGNATURE----- --Signature=_Mon__6_Oct_2003_09_55_52_+0200_um.cP=ST1Zj13T9n--