Re: Warm-cache prefetching - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Warm-cache prefetching
Date
Msg-id 12988.1134145125@sss.pgh.pa.us
Whole thread Raw
In response to Re: Warm-cache prefetching  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Warm-cache prefetching  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I can see that being useful for a single-user application that doesn't
> have locking or I/O bottlenecks, and doesn't have a multi-stage design
> like a database.  Do we do enough of such processing that we will _see_
> an improvement, or will our code become more complex and it will be
> harder to make algorithmic optimizations to our code?

The main concern I've got about this is the probable negative effect on
code readability.  There's a limit to the extent to which I'm willing to
uglify the code for processor-specific optimizations, and that limit is
not real far off.  There are a lot of other design levels we can work at
to obtain speedups that won't depend on the assumption we are running
on this-year's Intel hardware.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Upcoming PG re-releases
Next
From: Jan Wieck
Date:
Subject: Re: Foreign key trigger timing bug?