Side comment:
I understand what Wil is saying and I think he has a valid point. But
I believe the value of the point is now insignificant. The tiny bit of
contention that Will brings up here is about just how much disk access
is done by any given process. Eliminate disk reads and the process
speed
dding more memory. Then go
home.
-Original Message-
From: Wjhonson
To: u2-users
Sent: Fri, Mar 8, 2013 2:48 pm
Subject: Re: [U2] Unidata index and short-circuit evaluation
I didn't miss it.
The point of the request, was from the beginning to the ending.
Of course the firs
gt; To: u2-users
> Sent: Fri, Mar 8, 2013 1:17 pm
> Subject: Re: [U2] Unidata index and short-circuit evaluation
>
>
> On 08/03/13 21:03, Jeffrey Butera wrote:
>> While I'm on a roll... I often look at how to make queries run faster.
>> In short, we index a
yway. So doing it before or at
the same time as the other selects is irrelevant.
But yes. I based my recommendations on minimizing the number of disk
accesses ...
Cheers,
Wol
>
>
>
>
>
>
> -Original Message-
> From: Wols Lists
> To: u2-users
> Sent: F
Jeffery,
I would say #1 does the trick.
Any U2 TCL query evaluates from left to right. When one term eliminates the
record the query on that record stops, and the query continues to the next
record. So #1 is exactly your most effective, leaving the complex i-descriptor
to evaluate only the
are read again, then you should
run a single combined select which will do all accesses at the same instant.
-Original Message-
From: Wols Lists
To: u2-users
Sent: Fri, Mar 8, 2013 1:17 pm
Subject: Re: [U2] Unidata index and short-circuit evaluation
On 08/03/13 21:03, Jeffrey
On 08/03/13 21:03, Jeffrey Butera wrote:
> While I'm on a roll... I often look at how to make queries run faster.
> In short, we index all the commonly used data fields we can and (of
> course) it makes world of difference. However, I have some questions
> about optimal ways to query data using
