Re: hash index improving v3

On Fri, Sep 12, 2008 at 3:14 AM, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com> wrote:
> Alex Hunsaker napsal(a):
>>
>> On Wed, Sep 10, 2008 at 10:27 AM, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
>>>
>>> On Wed, Sep 10, 2008 at 8:47 AM, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>
>>> wrote:
>>>>
>>>> What locale did you use? It would be nice to have also comparing between
>>>> C
>>>> and any UTF8 locale. I think we should see big benefit when non C locale
>>>> is
>>>> used.
>>>
>>> Err yes this was UTF8, Ill see about doing a C locale.
>>>
>>
>> And here it with a C locale:
>>
>> pgbench -c1 -n -t100000 -f bench.sql
>> cvs head: tps = 5142.784262
>> v5: tps = 6169.405965
>
>
> If I look on both results
>
> C UTF8 difference
> -----------------------------------
> cvs head: 5140 5050 -2%
> v5: 6170 5750 -7%
> improvement: 20% 14%
>
> than I little bit wonder. I personally expected bigger difference of UTF8
> comparing between CVS a v5. This test also shows that locale selection has
> bigger impact on performance in v5 case, but result is still better than cvs
> head.

Right, I think part of it is I need to try again with a larger
dataset... The reason I did three runs before was because it was
variable between (v5 between 5700 and 6200). Also the query im doing
ming be two simplistic because it runs to fast, thats part of why I
get the variable speed between runs (i think...)

Suggestions?