Hi Robby,
Have you tried to run explain/profile on that query? As far as I
understand, it have 5000 PPConst operations. It's quite a number of
operations. So, there is a possibility, (at least in case of Sedna) you are
actually testing performance of the parser, query optimizer, memory
allocation.
Try to load these numbers as a simple XML document.
Regards,
Ivan
On Fri, Mar 15, 2013 at 4:08 PM, Robby Pelssers <robby.pelss...@nxp.com>wrote:
> Hi guys,
>
> Just wanted to share a little test I did yesterday. And I was pretty
> surprised by some findings. Maybe interesting for you to see what exactly
> is causing the slow performance. That it can be improved dramatically is
> proved by competition so to say :)
>
> Ps. This is in no way intended negatively but as a little trigger to even
> make Sedna faster.
>
>
> http://www.robbypelssers.blogspot.nl/2013/03/finding-duplicate-values-with-xquery.html
>
> Cheers,
> Robby
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Sedna-discussion mailing list
> Sedna-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sedna-discussion
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion