Re: Postgresql JDBC UTF8 Conversion Throughput - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: Postgresql JDBC UTF8 Conversion Throughput
Date
Msg-id Pine.BSO.4.64.0809191944370.18776@leary.csoft.net
Whole thread Raw
In response to Re: Postgresql JDBC UTF8 Conversion Throughput  (Paul Lindner <lindner@inuus.com>)
List 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

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Encoding issues
Next
From: Kris Jurka
Date:
Subject: Re: Q: use setObject also for int or string