RE: [HACKERS] inlining - Mailing list pgsql-hackers

From Stupor Genius
Subject RE: [HACKERS] inlining
Date
Msg-id 000001bd95f8$4f4398a0$6198accf@darren
Whole thread Raw
In response to Re: [HACKERS] inlining  (dg@illustra.com (David Gould))
Responses Re: [HACKERS] inlining  (Bruce Momjian <maillist@candle.pha.pa.us>)
RE: [HACKERS] inlining  ("Henry B. Hotz" <hotz@jpl.nasa.gov>)
List pgsql-hackers
> Btw, I sure wish someone would comment on the S_LOCK analysis even if only
> to tell me not to make such long posts as it wastes bandwidth. Or
> was it just too long to read?

I read it all! Great analysis of the situation and not a waste, IMHO.

One comment...when you ran the tests in succession, could the cache be
responsible for the timing groupings in the same test?  Should a
little program be run in between to "flush" the cache full of garbage
so each real run will miss?  Seem to recall a little program, in CUJ,
I think, that set up a big array and then iterated over it to trash
the cache.

Darren  aka  stuporg@erols.com

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] now 6.4
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] inlining