Re: PostgreSQL HardWare

I found when prototyping my Postgresql application that there
is a BIG diference in performance if the entire set of data
fits in RAM. Just about anything is fast if that is the
case. But when your data gets to be 10 or 100 times what
will fit is RAM it can slow down drastically. When you do
your testing you must use realistic sized test data. I wrote
some functions to produce random numbers and strings and them
COPYed them into tables.

In your case, even after years, the data will still fit all in
the RAM cache. You can expect good performance.

Also, Postgresql is very uneven. Some things it does well and
fast and then one small change to the SQL that should not matter
and it just dies. Sometimes when a querry is runing slow
you can re-write the SQL to something equivalent and see a
speedup. This is IMO one of the major diferances between
Postgresql and Oracle. Oracle is not so uneven while with
Postgresql very similar querries can have very diferent times
to complete. A lot depends on your exact SQL querry. I can
write one that would take hours even on a small table.

That second CPU will ONLY help you if more then one client
is connected to Postgresql at the same time or if the computer
has some other non-database task to run. So if you
expect much concurrent access go with multi-CPU setup if
not then go with a faster single CPU. In every case RAM
helps more then anything else. The more RAM the better.
At today's prices 1GB not unreasonable.

--- Fernado San Martin <snmartin(at)galilea(dot)cl> wrote:
> I mean seventy thousand in fact...
>
> the main question is that i have 70.000 records in one table, 90.000
> in the
> other one, but there it's a lot of backend process like triggers,
> pgsql
> functions, inserts, updates. So simple querys works very good but
> what about
> some hard work?, what you say it's that ammount of records it's not a
> problem?
>
> > i'm guessing he meant what he said, 70.000, which
> > to american audiences reads as seventy thousand
> > and is written as 70,000. european countries use
> > a period as the thousands separator rather than a
> > comma like we do.
> >
> > rjsjr
> >
> > > -----Original Message-----
> > > From: pgsql-general-owner(at)postgresql(dot)org
> > > [mailto:pgsql-general-owner(at)postgresql(dot)org]On Behalf Of
> > > Troy(dot)Campano(at)LibertyMutual(dot)com
> > > Sent: Friday, January 04, 2002 1:30 PM
> > > To: jwbaker(at)acm(dot)org; snmartin(at)galilea(dot)cl
> > > Cc: pgsql-general(at)postgresql(dot)org
> > > Subject: Re: [GENERAL] PostgreSQL HardWare
> > >
> > >
> > > Well did he mean 70.000 records or 70,000 records?
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Jeffrey W. Baker [mailto:jwbaker(at)acm(dot)org]
> > > Sent: Friday, January 04, 2002 2:02 PM
> > > To: Fernando San Martn Woerner
> > > Cc: pgsql-general(at)postgresql(dot)org
> > > Subject: Re: [GENERAL] PostgreSQL HardWare
> > >
> > >
> > >
> > >
> > > On Fri, 4 Jan 2002, Fernando San Martn Woerner wrote:
> > >
> > > > I need to build a postgresql database with 2 tables containing
> 70.000
> > > > records each one, but they'll increase their size in 4.000
> records
> > > > monthly and some triggers and functions will be running on this
> tables
> > > > plus other smaller tables less than 40.000 records.
> > >
> > > That's a really small database. You should be able to run it on
> > > practically
> > > any hardware, and probably store all the data in memory.
> > >
> > > -jwb
> > >
> > >
> > >
> > > ---------------------------(end of
> broadcast)---------------------------
> > > TIP 2: you can get off all lists at once with the unregister
> command
> > > (send "unregister YourEmailAddressHere" to
> majordomo(at)postgresql(dot)org)
> > >
> > > ---------------------------(end of
> broadcast)---------------------------
> > > TIP 4: Don't 'kill -9' the postmaster
> > >
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/users-lounge/docs/faq.html
>
>
>
> --
> Galilea S.A.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

=====
Chris Albertson
Home: 310-376-1029 chrisalbertson90278(at)yahoo(dot)com
Cell: 310-990-7550
Office: 310-336-5189 Christopher(dot)J(dot)Albertson(at)aero(dot)org

__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com