https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362002-05-06T20:49:59ZEcoinformatics RedmineMetacat - Bug #193: evaluate recursive search performancehttps://projects.ecoinformatics.org/ecoinfo/issues/193?journal_id=6642002-05-06T20:49:59ZJing Taotao@nceas.ucsb.edu
<ul></ul><p>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.</p> Metacat - Bug #193: evaluate recursive search performancehttps://projects.ecoinformatics.org/ecoinfo/issues/193?journal_id=6652013-03-27T21:13:35ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 193</p>