On 29 Sep 2000, Gunnar R|nning wrote:
> Tim Kientzle <kientzle@acm.org> writes:
>
> >
> > A custom converter may not really help; I experimented with that for
> > another project and it really didn't make that big of a difference.
> >
> > You might get some advantage by manually handling the converter object,
> > keeping a reference to it in the database handle so you don't have to
> > re-instantiate that class every time. That might help.
>
> Yup, this actually seems to take more time than the conversions themselves
> at the moment according to how OptimizeIT presents my application run.
>
> > a statement, convert just the arguments into bytes and emit the
> > complete statement.) I've had very good luck with this strategy
> > for building and caching mostly-static web pages within Java servlets.
>
> Good tip, but I think the next big leap in performance would be to improve
> the speed of the ResulSet get methods.
For JDBC2, I'm planning (may get done for 7.1) an alternate ResultSet
class that uses cursors. This would speed things up as the entire
resultset isn't received in one go. That's the biggest bottleneck of them
all.
Peter
--
Peter T Mount peter@retep.org.uk http://www.retep.org.uk
PostgreSQL JDBC Driver http://www.retep.org.uk/postgres/
Java PDF Generator http://www.retep.org.uk/pdf/
