From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Luke Lonergan <LLonergan(at)greenplum(dot)com> |
Cc: | simon(at)2ndquadrant(dot)com, zhouqq(at)cs(dot)toronto(dot)edu, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Warm-cache prefetching |
Date: | 2005-12-09 21:12:07 |
Message-ID: | 200512092112.jB9LC7O25604@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Luke Lonergan wrote:
> Bruce,
>
> It (the compute intensity optimization) is what we did for copy parsing,
> and it sped up by a factor of 100+.
>
> The rest of the copy path could use some work too.
>
> Yge virtual tuples in 8.1 are another example of grouping operations
> into more compact chunks instead of doing bits at a time.
>
> The l2 cache optimization could pay huge dividends for certain parts
> of the code path, like sorting for instance. A simple outer loop that
> strip mines in l2 sized chunks in sorting could speed things up 5 to
> 10 times in that section.
Yes, I can see COPY and sort being good for optimization because we
spend a large percentage of the command in a small section of the code.
I just don't know what other things have a similar localized operating
area.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-12-09 21:41:58 | Re: Warm-cache prefetching |
Previous Message | Luke Lonergan | 2005-12-09 20:39:08 | Re: Warm-cache prefetching |