[jira] [Commented] (TORQUE-36) Select performance problem with Sybase
[ https://issues.apache.org/jira/browse/TORQUE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103750#comment-15103750 ] Thomas Vandahl commented on TORQUE-36: -- Please note that Village is no longer used by Torque 4.0 > 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-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org
[jira] [Commented] (TORQUE-36) Select performance problem with Sybase
[ 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-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org
[jira] [Commented] (TORQUE-152) Torque issue with Record.getValue() using jtds jdbc driver for sqlserver
[ https://issues.apache.org/jira/browse/TORQUE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103751#comment-15103751 ] Thomas Vandahl commented on TORQUE-152: --- Village is not used anymore in Torque 4.0. > Torque issue with Record.getValue() using jtds jdbc driver for sqlserver > > > Key: TORQUE-152 > URL: https://issues.apache.org/jira/browse/TORQUE-152 > Project: Torque > Issue Type: Bug > Components: Runtime, Village >Affects Versions: 3.3 > Environment: windows xp >Reporter: Sethuraman Ramasubramanian >Assignee: Thomas Vandahl > Fix For: 3.3.1 > > Original Estimate: 120h > Remaining Estimate: 120h > > This is my code that cause a problem: > Criteria crit=new Criteria(); > crit.addSelectColumn(FilingDtlsPeer.FILING_NO); > crit.addJoin(FilingDtlsPeer.FILING_NO,CmpnyFilingPeer.FILING_NO); > crit.addJoin(CmpnyFilingPeer.COMPANY_ID,CompanyPeer.COMPANY_ID); > crit.add(CmpnyFilingPeer.COMPANY_ID,5); > List toBeFiledDtls=BasePeer.doSelect(crit); > for(Record r : toBeFiledDtls){ > System.out.println(r); > System.out.println(r.getValue(FilingDtlsPeer.FILING_NO)); > } > At this line "System.out.println(r.getValue(FilingDtlsPeer.FILING_NO));" I > get an error - Column name: filing_no does not exist! > The reason behind this is resultmetadata .getTableName() returns back an > empty string from jtds. > This is used in QueryDataSet(Connection conn, String > selectStmt)->schema.populate(resultSet.getMetaData(), > null)->col.populate(meta, i, tableName);->this.tableName = > rsmd.getTableName(columnNumber) > Since this tablename is null, in Record.getValue(String > columnName)->index(columnName)->index(table,colname) - Over here it fails to > find the table name and fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org