X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id B7C549DCA81 for ; Tue, 10 Jan 2006 11:31:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27113-02 for ; Tue, 10 Jan 2006 11:31:45 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.193]) by postgresql.org (Postfix) with ESMTP id 62B149DCC1E for ; Tue, 10 Jan 2006 10:41:26 -0400 (AST) Received: by xproxy.gmail.com with SMTP id s14so2718100wxc for ; Tue, 10 Jan 2006 06:41:31 -0800 (PST) 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=hRvqfIyq9R3vodXdVhuhFz4dvgWp2zpui1hsEao5foZvleVdGNHeNT6kgB/sg1zaTFc8F6SeC40wDmWAMNDPRoxNDIZn/8Rk5j9dqAjFQaG2DoaRPTKcriNf4O6Dp+b4x8Icc7GNN+piGURVrJhPJoJF/b2BpXrVWTQpy4em/+I= Received: by 10.70.25.16 with SMTP id 16mr6390953wxy; Tue, 10 Jan 2006 06:41:28 -0800 (PST) Received: by 10.70.55.9 with HTTP; Tue, 10 Jan 2006 06:41:27 -0800 (PST) Message-ID: Date: Tue, 10 Jan 2006 12:41:27 -0200 From: "Charles A. Landemaine" To: pgsql-performance@postgresql.org Subject: How to handle a large DB and simultaneous accesses? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200601/85 X-Sequence-Number: 16563 Hello, I have to develop a companies search engine (looks like the Yellow pages). We're using PostgreSQL at the company, and the initial DB is 2GB large, as it has companies from the entire world, with a fair amount of information. What reading do you suggest so that we can develop the search engine core, in order that the result pages show up instantly, no matter the heavy load and the DB size. The DB is 2GB but should grow to up to 10GB in 2 years, and there should be 250,000 unique visitors per month by the end of the year. Are there special techniques? Maybe there's a way to sort of cache search results? We're using PHP5 + phpAccelerator. Thanks, -- Charles A. Landemaine.