Re: Hint: parseSql(...) in AbstractJdbc2Statement.java can be optimized performance-wise

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: rw2xg7h02(at)sneakemail(dot)com
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Hint: parseSql(...) in AbstractJdbc2Statement.java can be optimized performance-wise
Date: 2008-08-18 21:58:38
Message-ID: 48A9F08E.6090505@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

rw2xg7h02(at)sneakemail(dot)com wrote:
> Hi,
>
> Just wanted to let you know, that the parseSql(...)-method can be optimized quite a bit by removing the many calls to p_sql.charAt and newsql.append. These could be replaced with local variables not requiring calls to be mutated (e.g. local char[]). I'm dealing with very long SQL-statements due to the use of Hibernate and parsing the SQL takes up quite some time - revealed by profiling tools.
>
> Just wanted to let you know, if you at some point would like to optimize the performance of the JDBC driver.

Got a patch that does this and some benchmarks to show it going faster?

-O

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Daniele Depetrini 2008-08-18 22:09:26 Re: Pooled connections idle timeout
Previous Message rw2xg7h02 2008-08-18 21:40:34 Hint: parseSql(...) in AbstractJdbc2Statement.java can be optimized performance-wise