From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "Thomas T(dot) Thai" <tom(at)minnesota(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: performance hit with --enable-debug |
Date: | 2001-01-14 17:58:16 |
Message-ID: | 26527.979495096@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> The effect in terms of query execution speed is probably minimal. The
>> problem is that the executables get about 15% larger, which can lead to
>> longer load times, more memory usage, and ultimately to some speed issues.
> Not sure about the longer load times.
I don't believe that either. The debug symbol tables aren't part of the
memory-resident image, they just sit out there on disk ... at least in
Unixen that I'm familiar with.
I think this is worth looking at more closely. I can't see any reason
that Tom should be seeing a 30x performance hit from --enable-debug;
there's something going on here that I don't understand.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-01-14 18:00:59 | Re: performance hit with --enable-debug |
Previous Message | Tom Lane | 2001-01-14 17:53:02 | Re: Re: performance hit with --enable-debug |