| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Paul Lindner <lindner(at)inuus(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Postgresql JDBC UTF8 Conversion Throughput |
| Date: | 2008-09-19 23:45:59 |
| Message-ID: | Pine.BSO.4.64.0809191944370.18776@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, 19 Sep 2008, Paul Lindner wrote:
> When you use 2 or more character sets getBytes(Charset) and getBytes(String)
> single-thread performance are about the same with getBytes(String) slightly
> ahead. ByteBuffer ends up being the big winner:
>
> Doing 10000000 iterations of each for string - 'abcd1234'
> 15662 getBytes(Charset)
> 14958 getBytes(String)
> 10098 via ByteBuffer
>
> In any case all of this only pertains to single thread performance. Our web
> apps are running on 8 and 16 core systems where contention is the biggest
> performance killer.
>
I see, so this wins even single threaded. In that case I've applied your
patch to CVS.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2008-09-20 00:34:43 | Re: Q: use setObject also for int or string |
| Previous Message | Kris Jurka | 2008-09-19 22:55:08 | Re: Encoding issues |