Re: [bdbxml] Cross Query Performance Issues
"Deepak Jois" <[email protected]> Tue, 21 Feb 2006 17:52:10 +0800
| Newsgroups | gmane.comp.db.dbxml.general |
|---|---|
| Message-ID | <[email protected]> |
> > - In any case, why does the first query take a disproportionately long
> > time as to not return even within an hour, when the second query which
> > seems equivalent returns almost instantaneously.
>
> This puzzled me for a while. My current corollary from looking at the
> query plan for the two queries is that it is to do with the size of the
> expressions on either side of the "=3D" operator. Can you try this query,
> and see if it is even faster:
>
> for $x in collection("enzyme.dbxml")/gnv_enzyme_pathway/
> db_entry[contains(enzyme_description,"cyclase")]/
> swissprot_reference_list/reference/@swissprot_accession_number
> for $z in collection("upt_swissprot.dbxml")/uniprot/
> entry[accession =3D $x]
> return ($z/name, $z/accession)
>
> If this is faster, then that may support my idea of what is going on.
Yes it is faster, and works for both keywords "Aristolochene" and
"cyclase" ! Now could you please backtrack and explain to me what it
is that you are trying to say when you write ''the size of the
expressions on either side of the '=3D' operator".
I have many such queries that are gonna involve joins between multiple
containers which contain different kinds of biological data,
interrelated by either a particular node or attribute.
Are there any best practises I can follow based on what you see so far?
Thanks
Deepak
P.S: Also, let me take this chance to say that this is by far the most
helpful mailing list I have come across. Keep up the great work.
------------------------------------------
To remove yourself from this list, send an
email to [email protected]