Re: Supporting SJIS as a database encoding - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject Re: Supporting SJIS as a database encoding
Date
Msg-id 0A3221C70F24FB45833433255569204D1F5E7D4A@G01JPEXMBYT05
Whole thread Raw
In response to Re: Supporting SJIS as a database encoding  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Supporting SJIS as a database encoding
List pgsql-hackers
From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Kyotaro
> HORIGUCHI
> <Using radix tree>
> $ time psql postgres -c 'select t.a from t, generate_series(0, 9999)' >
> /dev/null
> 
> real    0m22.696s
> user    0m16.991s
> sys    0m0.182s>
> 
> Using binsearch the result for the same operation was
> real    0m35.296s
> user    0m17.166s
> sys    0m0.216s
> 
> Returning in UTF-8 bloats the result string by about 1.5 times so it doesn't
> seem to make sense comparing with it. But it takes real = 47.35s.

Cool, 36% speedup!  Does this difference vary depending on the actual characters used, e.g. the speedup would be
greaterif most of the characters are ASCII?
 

Regards
Takayuki Tsunakawa





pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Is tuplesort_heap_siftup() a misnomer?
Next
From: Heikki Linnakangas
Date:
Subject: Re: GiST penalty functions [PoC]