Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 063C6632C25 for ; Wed, 14 Apr 2010 10:22:40 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 61172-01 for ; Wed, 14 Apr 2010 13:22:20 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com [74.125.82.174]) by mail.postgresql.org (Postfix) with ESMTP id 41266632D7A for ; Wed, 14 Apr 2010 10:21:44 -0300 (ADT) Received: by wyf19 with SMTP id 19so50188wyf.19 for ; Wed, 14 Apr 2010 06:21:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=EVedTswjAkCU3adfxZJFc3Sz7PNlRwQrxYByEYwbBRQ=; b=tA06kChf19tduR5qTPB2noLIPwfjYZ61gL3jTmOE7k6JrNGGLk43g8T+tisdvFQXjC fe3jA5h0vrIRQO5chrOruiZyRVqqek3kN5kO9ypZR2jg04SHDhql7oFAcJgMyZBwHEMC K0Tu73+fETatevFhL/GpuQp8ZK8n2cW7gU/Ow= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Xg8nLvGZAHyPyuHpVV+hTk15FzMW2gDWPd9UJpUj4DJhkFR5yOO/+Fm6Y2eOJmUCPo vB9vig/BZQMVebUqZzofPXicOVYlfRJb/iZxIPzB4JZkwrCUlP0K+mBO2ZBdAPtwCYL8 Cmc7061T5RvvD6mFG7Q66GW3m2XM7tXfZVKSI= MIME-Version: 1.0 Received: by 10.216.134.3 with HTTP; Wed, 14 Apr 2010 06:21:41 -0700 (PDT) In-Reply-To: References: <4BBF4FDD.3090008@2ndquadrant.com> Date: Wed, 14 Apr 2010 15:21:41 +0200 Received: by 10.216.86.85 with SMTP id v63mr4987256wee.32.1271251302056; Wed, 14 Apr 2010 06:21:42 -0700 (PDT) Message-ID: Subject: Re: PostgreSQL with Zabbix - problem of newbe From: Krzysztof Kardas To: Scott Marlowe Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.4 tagged_above=-10 required=5 tests=AWL=-0.400, BAYES_50=0.8 X-Spam-Level: X-Archive-Number: 201004/171 X-Sequence-Number: 38421 Hi all. Well I have used all Your recomendations but I still have no luck with performance tunning. The machine has a moments thas was utilized in 100%. The problem was I/O on disks. CPU's were busy on system interrupts. I have started again to look of I/O performance tunning and I have changed a synchronous_commit = off Ofcourse with risk that if there will be a power failure I will lose some data. But this is acceptable. This caused a monumental performance jump. From a machine that is utilized on 100%, machine is now sleeping and doing nothing. I have executed some sqls on huge tables like history and all has executed like lightning. Comparing to MySQL, PostgreSQL in this configuration is about 30 - 40% faster in serving data. Housekeeper is about 2 to 3 times faster!!!! Many thanks to all helpers and all PostgreSQL team. -- Greeting Krzysztof Kardas