| From: | Francisco J Reyes <fran(at)natserv(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, PostgreSQL performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: How number of columns affects performance |
| Date: | 2003-08-01 20:56:08 |
| Message-ID: | 20030801163346.V49062@zoraida.natserv.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 1 Aug 2003, Josh Berkus wrote:
> My attitude toward these normalization vs. performance issues is consistenly
> the same: First, verify that you have a problem. That is, build the
> database with everything in one table (or with child tables for Nullable
> fields, as above) and try to run your application. If performance is
> appalling, *then* take denormalization steps to improve it.
I think I understand your point, however it would be very laborious after
you do all development to find out you need to de-normalize.
On your experience at which point it would actually help to do this
de-normalization in PostgreSQL? I know there are numerous factors ,but any
feedback based on previous experiences would help.
Right now the work I am doing is only for company internal use. If I was
to ever do work that outside users would have access to then I would be
looking at 100+ concurrent users.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fernando Papa | 2003-08-01 21:17:17 | I can't wait too much: Total runtime 432478.44 msec |
| Previous Message | Josh Berkus | 2003-08-01 19:21:43 | Re: How number of columns affects performance |