| From: | Carlos Henrique Reimer <carlosreimer(at)yahoo(dot)com(dot)br> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | log_duration times |
| Date: | 2005-09-06 20:34:12 |
| Message-ID: | 20050906203412.32616.qmail@web53209.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi,
We want to discover how to improve the performance of an application and with that intention I turned on log_duration, log_statement=all and the time stamp escape character (%t) of log_line_prefix.
Subtracting the time stamp of the last SQL statement from the first one I disovered that the whole application takes about 10 seconds to run. Almost the same time we have at the client workstation.
Adding all the log_duration times I found almost 3 seconds (30% of the total time).
So, I realized that to improve performance it will be better to discover who is spending the 7 remaining seconds than making changes in database structure or SQL syntax.
How could I discover who is using the 7 remaining seconds? Network? ODBC? Application?
Thanks in advance!
Reimer
__________________________________________________
Converse com seus amigos em tempo real com o Yahoo! Messenger
http://br.download.yahoo.com/messenger/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Peterson | 2005-09-07 00:54:24 | Re: poor VACUUM performance on large tables |
| Previous Message | Tom Lane | 2005-09-06 17:42:59 | Re: Poor performance of delete by primary key |