X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 15BE3D1B482 for ; Tue, 30 Mar 2004 21:50:46 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 06220-09 for ; Tue, 30 Mar 2004 17:50:40 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id E8760D1D206 for ; Tue, 30 Mar 2004 17:50:37 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i2ULoZYn065242 for ; Tue, 30 Mar 2004 21:50:35 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i2ULkZfL064463 for pgsql-admin@postgresql.org; Tue, 30 Mar 2004 21:46:35 GMT From: Erland Sommarskog X-Newsgroups: comp.databases.ms-sqlserver, comp.databases.postgresql.admin, cz.comp.microsoft.sql, microsoft.public.il.hebrew.sqlserver, microsoft.public.sqlserver, microsoft.public.sqlserver.misc Subject: Re: what is the impact of Database size on Performemce Date: Tue, 30 Mar 2004 21:48:10 +0000 (UTC) Organization: Erland Sommarskog Lines: 37 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@telenordia.se User-Agent: Xnews/06.07.17 Mime-proxy/1.4.c.0 (Win32) To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/58 X-Sequence-Number: 13031 Avner (avnera@cvdo.com) writes: > I need some information to understand what is the impact of Database > size on the performemce. > > Few questions : > > 1. Is there any impact? Maybe. Maybe not. Depends whether you query the large table, and not the least how you query them, and what indexes you have. As a matter of fact, for the same amount of information, a database A twice as big as database B, could give better performance for retrieving a certain subset of that information, because in A data has been stored redudantly, maybe preaggregated. For instance, say that you have a transactions table for bank accounts, and you need to be able to retrieve the balance on a certain date. Saving the standings for each day is going to take up a lot of space, but it will be much faster to retrieve the historic balance, than adding up all transactions. > 2. Does one very large table impact the performence of the the whole DB, > meaning the overall performence and access the other tables. If the table just sits there, no. However, it will have an impact on backup operations. > 3. What are the ways to reduce the impact of the DB size on the DB > performence Good indexing is of course essential. -- Erland Sommarskog, SQL Server MVP, sommar@algonet.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp