From: | "Thomas T(dot) Thai" <tom(at)minnesota(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: performance hit with --enable-debug |
Date: | 2001-01-14 17:29:18 |
Message-ID: | Pine.NEB.4.21.0101141125460.531-100000@ns01.minnesota.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 14 Jan 2001, Peter Eisentraut wrote:
> Thomas T. Thai writes:
>
> > what kind of performance hit would i endure if i compiled with
> > --enable-debug on -current
>
> 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.
> Personally, I wouldn't worry about it too much, especially if you're
> running beta and want to track down potential bugs.
i'm running mnogosearch along with pgsql-current. and performance have
been just terrible to get results back on a resonable time. i couldn't
figure out so i check my ./configure flags. and there it was
--enable-debug. after sending my email to the list, i recompiled w/o debug
and now i can get my results back from a query in less than 2
seconds. before it was 59 secs if it returned at all. size of postgres
went down from 11.5 MB to a little less than 3mb. overall things seem
faster for inserts and selects for newly started backends too.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-01-14 17:37:00 | Re: performance hit with --enable-debug |
Previous Message | Tom Lane | 2001-01-14 16:50:08 | Re: to_char(date '2001-04-01', 'dd') results in 31 -- why? |