Subject | Re: Serious performance problems with PreparedStatement |
---|---|
Author | hlavac2 |
Post date | 2002-11-16T02:20:36Z |
--- In Firebird-Java@y..., "Roman Rokytskyy" <rrokytskyy@y...> wrote:
network level. Thus it seems it is not problem of JDBC driver (well,
at the first call to prepare statement it adds ~40ms looking for
correct Java encoding, but what the heck...) but database engine.
Database engine operation "op_prepare_statement" takes full 550ms to
return response! That is A LOT of time isn't it?
Unfortunaltely I won't be able to continue drilling into database
engine code... what should I do? Ask some of the engine developers?
Jan
> Can you check this execution times of this query using normalIt
> Statement with some real parameters? Also, it would be great if you
> compare it with performance in some native tool (ibconsole, etc.).
> might happen that it is not related to JDBC driver, but to theI have tracked the delay all the way through Java driver code down to
> database engine.
network level. Thus it seems it is not problem of JDBC driver (well,
at the first call to prepare statement it adds ~40ms looking for
correct Java encoding, but what the heck...) but database engine.
Database engine operation "op_prepare_statement" takes full 550ms to
return response! That is A LOT of time isn't it?
Unfortunaltely I won't be able to continue drilling into database
engine code... what should I do? Ask some of the engine developers?
Jan