From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Improved scanner performance |
Date: | 2002-04-20 17:20:31 |
Message-ID: | Pine.LNX.4.30.0204201248270.688-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane writes:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Tom Lane writes:
> >> I had the idea that -CF would enlarge the lexer tables quite a bit ---
> >> what's the change in executable size?)
>
> > +150 kB
>
> > I've also looked at -CFe, which is supposedly the next slowest level, but
> > it doesn't do nearly as well.
>
> Ouch; that sounds like about a ten percent increase in the size of
> the backend executable. That's enough to reach my threshold of pain;
> is the long-literal issue worth that much?
Here's a breakdown of the postmaster file sizes and the wall-clock run
time of the long-literal test:
no options 1749912 1m58.688s
-CFe 1754315 1m49.223s
-CF 1817621 1m43.780s
-CFa 1890197 1m45.600s
(These numbers are different than yesterday's because they don't have
profiling and debugging overhead.)
Seeing this, I think -CF should be OK space and time-wise.
> How much of your reported improvement is due to -CFa, and how much to
> the coding improvements you made?
As I recall it, probably a third of the overall improvement came from
using -CF[a].
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-20 17:25:00 | Re: Improved scanner performance |
Previous Message | Tom Lane | 2002-04-20 16:16:37 | Re: Documentation on page files |