X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 270CC329D15 for ; Mon, 27 Sep 2004 18:45:03 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 69142-08 for ; Mon, 27 Sep 2004 17:44:57 +0000 (GMT) Received: from mail.musicrebellion.com (dsl093-203-229.ind1.dsl.speakeasy.net [66.93.203.229]) by svr1.postgresql.org (Postfix) with ESMTP id 4C4E2329CFB for ; Mon, 27 Sep 2004 18:44:58 +0100 (BST) Received: from [10.0.1.102] (helo=musicrebellion.com ident=kris) by mail.musicrebellion.com with asmtp (Exim 4.34 #1 (Debian)) id 1CBzYV-0001CP-3j for ; Mon, 27 Sep 2004 12:44:55 -0500 Message-ID: <41585198.6080709@musicrebellion.com> Date: Mon, 27 Sep 2004 12:44:56 -0500 From: Kris Kiger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 X-Accept-Language: en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: tsearch2 poor performance References: <71E37EF6B7DCC1499CEA0316A2568328DC9DF0@loki.wc.globexplorer.net> <4158409E.8060109@musicrebellion.com> <41584E49.5040301@musicrebellion.com> <41584F91.6000109@commandprompt.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/253 X-Sequence-Number: 14956 Josh, I am running my tests on a dual processor PIII 1 GHz machine with 2Gb of RAM. There are four hard drives set up. One for OS/logging and three in a raid-5 configuration for the postgres data directory. Kris Joshua D. Drake wrote: > Hello, > I might of missed this on a previous message, BUT what type of > hardware are we dealing with here? Is it possible that we just don't > have enough IO/RAM to push this? > J > Kris Kiger wrote: > >> Oleg, >> Thanks for the help on this. >> The query I used to return the 508 number is: >> SELECT * FROM stat('SELECT vector FROM product') ORDER BY >> ndoc desc, word ; >> Testing says, the more words I use, the faster the query is. My >> original search word, 'oil', appears in 226,357 documents 233,266 >> times. As far as distinct words go, 'oil' is middle of the road for >> occurences. As it is set up now, the best search time I am getting >> on this single word is roughly 22 seconds. Kris >> >> Oleg Bartunov wrote: >> >>> Kris, >>> >>> do you actually have only 508 disctinct words ? Could you try >>> more complex queries, say 2-3 words. Does these queries run faster ? >>> Oleg >>> On Mon, 27 Sep 2004, Kris Kiger wrote: >>> >>>> Regardless of caching, the queries are still taking 19~20 seconds >>>> to run >>>> on the 3,000,000 rows. I've played with performance tuning and >>>> nothing >>>> seems to make much of a difference. If I am reading that list from >>>> stat >>>> correctly, then I am operating on 508 distinct words. Is this the >>>> performance I should expect from tsearch2? Or is something still >>>> awry? >>>> I'm inclined to think something else is wrong, after reading some >>>> other people's tsearch performance stats. Thanks! >>>> >>>> Kris >>> >>> Regards, >>> Oleg >> -- ______________________________ Kris Kiger Software Developer Digonex Technologies, Inc. 317.638.4174 Fax CONFIDENTIALITY NOTICE: The information in this transmission is private, confidential, may be legally privileged, is property of the sender and is intended solely for the use of the addressee. If you are not the addressee, you should not read, disclose, distribute, copy, use or rely upon the information contained in this transmission. If you have received this transmission in error please delete or destroy it and notify DIGONEX TECHNOLOGIES, INC. immediately at (317) 638-4154.