From: | Erland Sommarskog <sommar(at)algonet(dot)se> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: what is the impact of Database size on Performemce |
Date: | 2004-03-30 21:48:10 |
Message-ID: | Xns94BCF1DFDDA4CYazorman@127.0.0.1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Avner (avnera(at)cvdo(dot)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(at)algonet(dot)se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2004-03-30 22:11:22 | Re: Deleting a database |
Previous Message | Manuel Sugawara | 2004-03-30 21:33:03 | Re: tweaking scan.l |