| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Overhead for stats_command_string et al, take 2 |
| Date: | 2006-06-22 21:41:41 |
| Message-ID: | 7376.1151012501@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> Tom Lane wrote:
>> It'd be interesting to compare 8.1 and HEAD for the no-overhead case;
>> I don't think you need to redo all four cases, but I'd like to see that one.
> 8.1: 50,50,49
> HEAD: 49,48,49
OK, so that seems comparable to my results on a dual Xeon ... probably,
both your machine and my newer one have fast-to-read clock hardware.
We need to get some numbers from one of the people who have complained
about EXPLAIN ANALYZE overhead.
I'll have to try the stats-collection-active case on my machines, too.
I was still planning to look into removing the buffer process to reduce
context-swap overhead for stats collection ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2006-06-22 22:04:05 | Re: [CORE] GPL Source and Copyright Questions |
| Previous Message | Stefan Kaltenbrunner | 2006-06-22 21:37:31 | Re: Overhead for stats_command_string et al, take 2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-06-22 22:18:12 | Re: Overhead for stats_command_string et al, take 2 |
| Previous Message | Stefan Kaltenbrunner | 2006-06-22 21:37:31 | Re: Overhead for stats_command_string et al, take 2 |