From: | Daniel Bausch <bausch(at)dvs(dot)tu-darmstadt(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Parallel Seq Scan |
Date: | 2015-01-27 07:02:37 |
Message-ID: | 87d2601zaq.fsf@gelnhausen.dvs.informatik.tu-darmstadt.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi PG devs!
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Wait for first IO, issue second IO request
>> Compute
>> Already have second IO request, issue third
>> ...
>
>> We'd be a lot less sensitive to IO latency.
>
> It would take about five minutes of coding to prove or disprove this:
> stick a PrefetchBuffer call into heapgetpage() to launch a request for the
> next page as soon as we've read the current one, and then see if that
> makes any obvious performance difference. I'm not convinced that it will,
> but if it did then we could think about how to make it work for real.
Sorry for dropping in so late...
I have done all this two years ago. For TPC-H Q8, Q9, Q17, Q20, and Q21
I see a speedup of ~100% when using IndexScan prefetching + Nested-Loops
Look-Ahead (the outer loop!).
(On SSD with 32 Pages Prefetch/Look-Ahead + Cold Page Cache / Small RAM)
Regards,
Daniel
--
MSc. Daniel Bausch
Research Assistant (Computer Science)
Technische Universität Darmstadt
http://www.dvs.tu-darmstadt.de/staff/dbausch
From | Date | Subject | |
---|---|---|---|
Next Message | Haribabu Kommi | 2015-01-27 07:04:48 | Re: Providing catalog view to pg_hba.conf file - Patch submission |
Previous Message | Noah Misch | 2015-01-27 05:24:05 | Re: jsonb, unicode escapes and escaped backslashes |