From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gary Doades <gpd(at)gpdnet(dot)co(dot)uk> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Strange Create Index behaviour |
Date: | 2006-02-15 21:51:23 |
Message-ID: | 20005.1140040283@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Gary Doades <gpd(at)gpdnet(dot)co(dot)uk> writes:
> Interestingly, if I don't delete the table after a run, but just drop
> and re-create the index repeatedly it stays a pretty consistent time,
> either repeatedly good or repeatedly bad!
This is consistent with the theory of a data-dependent performance
problem in qsort. If you don't generate a fresh set of random test
data, then you get repeatable runtimes. With a new set of test data,
you might or might not hit the not-so-sweet-spot that we seem to have
detected.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-02-15 23:28:29 | qsort again (was Re: [PERFORM] Strange Create Index behaviour) |
Previous Message | Tom Lane | 2006-02-15 21:48:56 | Re: Strange Create Index behaviour |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-02-15 23:28:29 | qsort again (was Re: [PERFORM] Strange Create Index behaviour) |
Previous Message | Tom Lane | 2006-02-15 21:48:56 | Re: Strange Create Index behaviour |