On 2015-09-02 16:02:00 -0700, Peter Geoghegan wrote: > On Wed, Sep 2, 2015 at 3:13 PM, Andres Freund <and...@anarazel.de> wrote: > > That's just a question of how to formulate this though? > > > > pg_rfetch(((char *) state->memtuples ) + 3 * sizeof(SortTuple) + > > offsetof(SortTuple, tuple))? > > > > For something heavily platform dependent like this that seems ok. > > Well, still needs to work for tuplestore, which does not have a SortTuple.
Isn't it even more trivial there? It's just an array of void*'s? So prefetch(state->memtuples + 3 + readptr->current)? > Because of the way tuples are fetched across translation unit > boundaries in the cases addressed by the patch, it isn't hard to see > why the compiler does not do this automatically (prefetch instructions > added by the compiler are not common anyway, IIRC). Hardware prefetchers just have gotten to be rather good and obliterated most of the cases where it's beneficial. I'd be interested to see a perf stat -ddd comparison to the patch with/without prefetches. It'll be interesting to see how the number of cache hits/misses and prefetches changes. Which microarchitecture did you test this on? -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
