Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 8CCA59FB475 for ; Mon, 16 Oct 2006 06:17:05 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 30237-05 for ; Mon, 16 Oct 2006 06:17:02 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 564299FB470 for ; Mon, 16 Oct 2006 06:17:02 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by svr4.postgresql.org (Postfix) with ESMTP id B46B85AF043 for ; Mon, 16 Oct 2006 09:17:00 +0000 (GMT) Received: by py-out-1112.google.com with SMTP id d80so2325691pyd for ; Mon, 16 Oct 2006 02:15:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hII4LK2MZRFrrqavgCzRnNfWw032b1K9esSnRfUxYDOCuEa1nR+WjCznbLvv3eVDY5hlg1xbtOHi1zOoo2rFNEvFx7q7vH6Bum0+UAO7qToZRyAnvNbC5una9DfAXLyGh91WrLlcicVAAP5DvltW2aRH2xZrndX3KwUg18tEliQ= Received: by 10.35.95.1 with SMTP id x1mr12409033pyl; Mon, 16 Oct 2006 02:15:58 -0700 (PDT) Received: by 10.35.33.6 with HTTP; Mon, 16 Oct 2006 02:15:58 -0700 (PDT) Message-ID: <7be3f35d0610160215v21edbe48vc144200a83f41dd0@mail.gmail.com> Date: Mon, 16 Oct 2006 11:15:58 +0200 From: "Harald Armin Massa" To: pgsql-performance@postgresql.org Subject: measuring shared memory usage on Windows MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.009 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, SPF_NEUTRAL X-Spam-Level: * X-Archive-Number: 200610/286 X-Sequence-Number: 21415 Hello, Shridhar Daithankar and Josh Berkus write on http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html shared_memory """ There is one way to decide what is best for you. Set a high value of this parameter and run the database for typical usage. Watch usage of shared memory using ipcs or similar tools. A recommended figure would be between 1.2 to 2 times peak shared memory usage. """ I tried to find a way to do this on windows. Scanning all the lines of perfmon memory options, I could not see anithing like "shared memory usage". Googling for "shared memory usage" just drove me to some ancient WRONG information that PostgreSQL is not possible on Windows because of lacking shared memory. (guess that was for Windows 95 or similiar) So: has anybody a hint how I can check how much shared_memory is really used by PostgreSQL on Windows, to fine tune this parameter? I learned the hard way that just rising it can lead to a hard performance loss :) Harald --=20 GHUM Harald Massa persuadere et programmare Harald Armin Massa Reinsburgstra=DFe 202b 70197 Stuttgart 0173/9409607 - Python: the only language with more web frameworks than keywords.