X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 96046D1D674 for ; Wed, 19 Nov 2003 02:32:01 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 70512-04 for ; Tue, 18 Nov 2003 22:31:34 -0400 (AST) Received: from svana.org (svana.org [203.20.62.76]) by svr1.postgresql.org (Postfix) with ESMTP id 4CC2ED1B4E8 for ; Tue, 18 Nov 2003 22:31:30 -0400 (AST) Received: from kleptog by svana.org with local (Exim 3.35 #1 (Debian)) id 1AMI7M-0005oU-00; Wed, 19 Nov 2003 13:30:56 +1100 Date: Wed, 19 Nov 2003 13:30:56 +1100 From: Martijn van Oosterhout To: Rick Gigger Cc: "scott.marlowe" , PgSQL General ML Subject: Re: performance problem Message-ID: <20031119023055.GA22116@svana.org> Reply-To: Martijn van Oosterhout Mail-Followup-To: Rick Gigger , "scott.marlowe" , PgSQL General ML References: <021a01c3ae43$3b25a2f0$0700a8c0@trogdor> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline In-Reply-To: <021a01c3ae43$3b25a2f0$0700a8c0@trogdor> User-Agent: Mutt/1.3.28i X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6 X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522 48A7 6394 F08A 0DC6 7BE6 X-PGP-Key-URL: X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/975 X-Sequence-Number: 52625 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 18, 2003 at 04:54:59PM -0700, Rick Gigger wrote: > > That's VERY high. When postgresql has to manage a lot of buffers it > > actually is slower than letting the kernel in Linux or BSD do it for yo= u. >=20 > Even if you've got the memory to spare? Does postgres actually slow down > just because it's slower to manager a lot of them just or because you're > taking the memory away from the kernel so the kernel has to swap more? It's a combination. Any buffer that's stored in the postgresql cache is also in the kernel cache so that's just slightly inefficient. The kernel pool manager tends to be more optimised for handling large numbers of buffers. Because it's the kernel is can tailor for hardware quirks like high memory and bounce buffers and such. And when you're not using your shared memory it's wasted but the kernel can reallocate any memory it likes for any purpose. Hope this helps, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > "All that is needed for the forces of evil to triumph is for enough good > men to do nothing." - Edmond Burke > "The penalty good people pay for not being interested in politics is to be > governed by people worse than themselves." - Plato --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/utXfY5Twig3Ge+YRAo27AKDX3pbDmn4MbMyCcsH03xHIRVW8igCgmZdo 7x9/f6WhiT/bvOXS4c3mOuM= =OTvw -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q--