Re: performance hit with --enable-debug

From: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "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-15 18:37:40
Message-ID: 20010115183740.C1236@quartz.newn.cam.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Jan 14, 2001 at 12:58:16PM -0500, Tom Lane wrote:
> 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.

I suppose something to try is compile with --enable-debug, then strip the
resultant executable, and see if it is as fast as (should be identical to?)
executable generated without --enable-debug..

Cheers,

Patrick

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matt Doucleff 2001-01-15 18:53:08 Re: Need "InBetween" (not just Before and After) Trigger
Previous Message Brian C. Doyle 2001-01-15 18:19:31 Date help