Issue Details (XML | Word | Printable)

Key: DERBY-1996
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Derby

DatabaseMetaData.getColumns() takes long time to return columns for a particular schema of Apache JDO TCK

Created: 24/Oct/06 06:30 PM   Updated: 08/Jul/09 02:10 PM
Return to search
Component/s: SQL
Affects Version/s: 10.2.1.6
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  Size
Zip Archive testcase.zip 2006-10-24 06:31 PM Andy Jefferson 59 kB
Issue Links:
Reference
 

Urgency: Normal
Issue & fix info: Repro attached
Bug behavior facts: Performance


 Description  « Hide
When running the Apache JDO "TCK", JPOX needs to query the columns for a particular schema, and so uses DatabaseMetaData.getColumns(null, schemaName, null, null). This takes the order of 3 minutes on a dual-core Pentium 3GHz (with large ram). I've cut the JPOX part down to a stand-alone test (will attach it).

Thing to note is that with only the schema files d_* installed it takes the order of 20secs. When the schema_* files are also installed then performance goes downhill fast (even though they are in different schemas ... all *.sql file represents a different schema). No point in me postulating what could be the issue since you guys are the Derby experts.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson made changes - 24/Oct/06 06:31 PM
Field Original Value New Value
Attachment testcase.zip [ 12343570 ]
Mike Matrigali made changes - 06/May/07 09:17 PM
Component/s SQL [ 11408 ]
Bernt M. Johnsen made changes - 07/May/07 11:36 AM
Link This issue is related to DERBY-2584 [ DERBY-2584 ]
Knut Anders Hatlen made changes - 08/Jul/09 02:10 PM
Issue & fix info [Repro attached]
Bug behavior facts [Performance]
Issue Type Bug [ 1 ] Improvement [ 4 ]