Preston,
Let me suggest a way to track down our performance issues in VXQuery.
Let's approach our queries one at a time. First, let's start with the
single collection, scan-based queries and reason about their performance
in comparison to Saxon. As an even smaller goal, can you take your first
query and report running times on the 250MB of data alongwith Saxon's
running times?
Thanks,
Vinayak
On 11/29/13, 12:48 PM, Eldon Carman wrote:
The query plans are so big, I attached a document with the queries and
plans.
On Wed, Nov 27, 2013 at 8:53 PM, Vinayak Borkar <[email protected]
<mailto:[email protected]>> wrote:
Preston,
For each query, please send the following:
1. The query
2. The translated logical plan
3. The optimized physical plan
Thanks,
Vinayak
On 11/27/13, 8:16 PM, Eldon Carman wrote:
It appears that our query process is taking longer than
expected. I have
created a small set of sensors to test our benchmark queries.
The data set
is about 250 MB and the queries execute in 10 to 20 seconds with
the SAXON
XSLT processor. When I tried a few of the queries on VXQuery,
the process
ran for one hour and still did not complete. I am now looking
into where
the time is being spent for our query and see why its taking so
long.
