Re: Supporting SJIS as a database encoding

From: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
To: 'Kyotaro HORIGUCHI' <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: "hlinnaka(at)iki(dot)fi" <hlinnaka(at)iki(dot)fi>, "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "ishii(at)sraoss(dot)co(dot)jp" <ishii(at)sraoss(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Supporting SJIS as a database encoding
Date: 2016-09-08 07:09:51
Message-ID: 0A3221C70F24FB45833433255569204D1F5E7D4A@G01JPEXMBYT05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)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 greater if most of the characters are ASCII?

Regards
Takayuki Tsunakawa

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2016-09-08 07:12:30 Re: GiST penalty functions [PoC]
Previous Message Heikki Linnakangas 2016-09-08 07:01:40 Re: Is tuplesort_heap_siftup() a misnomer?