You've shown that the query takes up a lot of CPU, and that it is
slower than you would like. We have an idea as to how big the table
is (not very), and we know that you have done your homework and have
vacuum analyzed.
Next we need the query in question (so we can check for some of the
more well known performance pitfalls like using IN on large result
sets), and also the explain output (so we can see what PostgreSQL
thinks of your query). You also might want to consider including the
schema of the tables involved.
Jason
Gurudutt <guru@indvalley.com> writes:
> Hi,
>
> I have a pentium III server, running on RHL 7.1 with 256 MB RAM,
>
> The following is output of the "top" command for query which involves
> fetch from a table with about MAX of 10,000 rows.
>
> -------------------------------------TOP------------------------------
> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
>
> 3174 postgres 19 0 3328 3328 2672 R 99.0 1.3 0:58 postmaster
> 1199 nobody 9 0 3728 3728 2704 S 0.5 1.4 0:03 httpd
> 3035 root 10 0 1048 1048 840 R 0.3 0.4 0:15 top
> 1 root 8 0 544 544 472 S 0.0 0.2 0:04 init
> 2 root 9 0 0 0 0 SW 0.0 0.0 0:00 keventd
> 3 root
>
>
> Now, my question is, it takes ages(2 mints) for the query to run (regularly
> VACUUM ANALYZED Database) and if you look closely at the resources
> consumed by the postgres, it is almost taking away 100% CPU time.
>
> How can we make it faster and to consume less resources ??
>
> Can anybody suggest the steps they are taking for time-critical
> applications to run efficiently.
>
> Thanks in advance
>
> --
> Best regards,
> Gurudutt mailto:guru@indvalley.com
>
> Life is not fair - get used to it.
> Bill Gates
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org