X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 11E18B43E2B for ; Fri, 4 Jul 2003 16:41:53 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 49074-06 for ; Fri, 4 Jul 2003 13:41:42 -0300 (ADT) Received: from hot.ee (mail.hot.ee [194.126.101.94]) by svr1.postgresql.org (Postfix) with ESMTP id 064E4B43E24 for ; Fri, 4 Jul 2003 13:41:42 -0300 (ADT) Received: from localhost (relay2 [127.0.0.1]) by hot.ee (Postfix) with ESMTP id 8BEF2109007 for ; Fri, 4 Jul 2003 19:41:41 +0300 (EEST) Received: from hot.ee ([127.0.0.1]) by localhost (relay2 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01345-05 for ; Fri, 4 Jul 2003 19:41:41 +0300 (EEST) Received: from future.ee (80-235-33-206-dsl.mus.estpak.ee [80.235.33.206]) by hot.ee (Postfix) with ESMTP id 1666D108E8B for ; Fri, 4 Jul 2003 19:41:41 +0300 (EEST) Message-ID: <3F05AF44.6080601@future.ee> Date: Fri, 04 Jul 2003 19:45:56 +0300 From: Kaarel User-Agent: Mozilla/5.0 (X11; U; Linux i686; et-EE; rv:1.3) Gecko/20030313 X-Accept-Language: et, en-gb MIME-Version: 1.0 To: pgsql-advocacy@postgresql.org Subject: About the default performance Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by mail.hot.ee X-Archive-Number: 200307/32 X-Sequence-Number: 1556 The problem is that people often benchmark the so called vanilla installation of PostgreSQL. I understand why the PostgreSQL team has decided to have an overly conservative default conf file. But no matter what the reason is or who's to blame that a tester has not tuned PostgreSQL configuration, the word is being spread that PostgreSQL is featurerich but _slow_. The ongoing discussion currently in performance list is just one example. I have seen it announce more than once: "we did not do any configuration tuning on the test systems". Take http://www.hwaci.com/sw/sqlite/speed.html as another example. "The PostgreSQL and MySQL servers used were as delivered by default on RedHat 7.2. (PostgreSQL version 7.1.3 and MySQL version 3.23.41.) No effort was made to tune these engines. Note in particular the the default MySQL configuration on RedHat 7.2 does not support transactions." I remember a discussion in the general list about having multiple default conf files to choose from. Ala low-end, average and high-end installations. A tool to read some system information and dynamically generating a proper configuration file was also mentioned. The other issue that a lot of new PostgreSQL users seem to have is the VACUUM ANALYZE. They just don't know about it. Perhaps some more active ones will read the documentation or ask for help in email lists. But a lot of them are surely leaving things and thinking of PostgreSQL as a slow system. Remember they too spread the word of their experience. I'm not an expert of PostgreSQL by any means I have just been reading PostgreSQL email lists for only about a month or so. So I believe I have read that there is a auto-vacuum being worked on? In my opinion this should be included in the main installation by default. This is just the kind of job that a machine should do...when a big portion of data has changed do VACUUM ANALYCE automagically. Is these improvements actually being implemented and how far are they? The technical side of these problems is not for this list of course. However the "side-effects" (reputation of being slow) of these problems direclty relate to advocacy and PostgreSQL popularity. Maybe these problems are already worked on or maybe I'm over exaggerating the situation but I do believe solving these issues would only benefit PostgreSQL. Just my 2 c Kaarel