| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Assert Levels |
| Date: | 2008-09-21 22:19:36 |
| Message-ID: | Pine.GSO.4.64.0809211812110.27828@westnet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 19 Sep 2008, Tom Lane wrote:
> Well, there are certain things that --enable-cassert turns on that are
> outrageously expensive...I don't think anyone knows what the performance
> impact of just the regular Asserts is; it's been too long since these
> other things were stuck in there.
The next time I'm doing some performance testing I'll try to quantify how
much damage the expensive ones do by playing with pg_config_manual.h.
Normally I'm testing with 1GB+ of shared_buffers which makes the current
assert scheme unusable. If I could run with asserts on only only lose a
small amount of performance just by disabling the clobber and context
checking, that would be valuable to know. Right now I waste a fair amount
of time running performance and assert builds in parallel.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-09-21 22:32:45 | Re: parallel pg_restore |
| Previous Message | Tom Lane | 2008-09-21 22:15:21 | Re: parallel pg_restore |