Select performance problem with Sybase
--------------------------------------
Key: TORQUE-36
URL: http://issues.apache.org/jira/browse/TORQUE-36
Project: Torque
Type: Bug
Components: Runtime
Versions: 3.2
Environment: Java 1.4.2 on solaris 10 against Sybase 12.5.2
Reporter: Joe Carter
Selects via Torque perform 2-3 times slower than when doing the identical
statement via JDBC.
I took the SQL produced by Torque using p6spy to capture it.
I manually implemented the same SQL as a raw query and a prepared statement
obtaining a SQL connection from Torque.getConnection() to eliminate any
differences in the pooling etc.
I then ran performance tests against the 3 types.
The ratio in performance (big is slower) was 10-4-3 for standard Torque, raw
and then prepared statements.
The performance hit was definately against the database as we're seeing similar
performance improvements
on production systems with the database CPU usage dropping dramatically with
some gains on the calling tomcat server.
The suspicion is that metadata is being retrieved on every select but p6spy
unfortunately does not
support the reporting of this so this cannot be confirmed.
Note that the tests were performed without p6spy in the loop.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
