| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bison state table |
| Date: | 2019-01-25 23:49:50 |
| Message-ID: | 20190125234949.GI12076@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 25, 2019 at 05:38:59PM -0500, Bruce Momjian wrote:
> With our scanner keywords list now more cache-aware, and with us
> planning to use Bison for years to come, has anyone ever looked at
> reordering the bison state machine array to be more cache aware, e.g.,
> having common states next to each other rather than scattered around the
> array?
Do we have a pretty good idea of what commonly grouped states are, or
at least a way to get some not-awful estimates of what they are?
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-01-25 23:55:56 | Re: Bison state table |
| Previous Message | David Fetter | 2019-01-25 23:48:58 | Re: crosstab/repivot...any interest? |