From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | stuporg(at)erols(dot)com (Stupor Genius) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org, dg(at)illustra(dot)com |
Subject: | Re: [HACKERS] inlining |
Date: | 1998-06-12 12:21:18 |
Message-ID: | 199806121221.IAA10695@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
Yes, that is a good point. When testing in a loop, the function is in
the cache, while in normal use, the function may not be in the cache
because of intervening instructions.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1998-06-12 14:42:58 | Re: [HACKERS] S_LOCK reduced contention |
Previous Message | Stupor Genius | 1998-06-12 11:50:34 | RE: [HACKERS] inlining |