[ https://issues.apache.org/jira/browse/TORQUE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103749#comment-15103749
]
Thomas Vandahl commented on TORQUE-36:
--------------------------------------
Yes it was. Yes the problem may also apply to other databases. Many JDBC drivers cache metadata
internally, however.
> Select performance problem with Sybase
> --------------------------------------
>
> Key: TORQUE-36
> URL: https://issues.apache.org/jira/browse/TORQUE-36
> Project: Torque
> Issue Type: Bug
> Components: Runtime, Village
> Affects Versions: 3.2
> Environment: Java 1.4.2 on solaris 10 against Sybase 12.5.2
> Reporter: Joe Carter
> Assignee: Thomas Vandahl
> Fix For: 3.3.1
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org