From: | Gunnar R|nning <gunnar(at)candleweb(dot)no> |
---|---|
To: | kientzle(at)acm(dot)org |
Cc: | PostgreSQL general mailing list <pgsql-general(at)postgresql(dot)org>, "Keith L(dot) Musser" <kmusser(at)idisys(dot)com> |
Subject: | Re: Re: JDBC Performance |
Date: | 2000-09-29 10:15:45 |
Message-ID: | x6em23ld0u.fsf@thor.candleweb.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tim Kientzle <kientzle(at)acm(dot)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.
Regards,
Gunnar
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Lang | 2000-09-29 13:12:37 | Re: Login Problems. |
Previous Message | Gunnar R|nning | 2000-09-29 10:08:50 | Re: RE: JDBC Performance |