Hello again!
Sorry for the late reply. And thank you for sending us the data!
Both the queries you had profiled in previous letters executed fast on my
machine:
for $i in index-scan("chemicalcontent_id", "", "GE")/@id return string($i)
and
for $doc in collection("chemicalContent/released") return document-uri($doc)
it took less than a second to execute each of them. I had executed queries
on locally through built-in terminal se_term.
You noticed that:
Serializing and sending that data over the wire… takes like forever.. >> 1
minute.
Seems that slowdown can be achieved during connection to Sedna and sending
query results. Is Sedna server located on remote host? What driver do you
use?
--
I've tried some tests on generated data. As expected, the more schema of
individual documents differs from each other, the more performance
degradation is observed. But in case of similar or not very different
documents (which is yours) Sedna performs satisfactory fast. Hope that we
will resolve your performance issue.
Best regards,
Konstantin Abakumov
------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion