Project

General

Profile

Bug #193

evaluate recursive search performance

Added by Matt Jones over 18 years ago. Updated over 17 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
metacat
Target version:
Start date:
04/09/2001
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
193

Description

Need to evaluate performance of recursive searches more thoroughly and, if they
turn out to be as fast as searches using the XML_INDEX table, then we need to
diable the use of the xml_index table.


Related issues

Blocks Metacat - Bug #238: query performanceResolved06/19/2001

History

#1 Updated by Jing Tao over 17 years ago

Uniform xml documents were applied to test the query performance in both Oracle and Postgresql.To Oracle, path query has same performance as nested query.But in Postgresql, the performance is very different. As depth of doucment increasing, the time difference increases too. For example, when depth=8, nested query need about 198 seconds, but paht query (using xml_index table) only need 105 seconds.So, probably it is good to keep xml_index table. Metacat isnot designed only for Oracle.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 193

Also available in: Atom PDF