Colin:
There's something wrong here. Here's what I get when I do some selects:
A non-indexed select.
4 Demo (0)-> .X3-1
TIME
13:29:28 Aug 16 2007
SELECT GLPOST WITH CLIENTNO = "605"
33137 records selected to list 0.
TIME
13:29:33 Aug 16 2007
4 Demo (0)>> CLEARSELECT
Supposedly an indexed select.
4 Demo (0)-> .X2,4,2
TIME
13:30:40 Aug 16 2007
SELECT GLPOST WITH INDEX_2 = "0605]"
33137 records selected to list 0.
TIME
13:30:57 Aug 16 2007
4 Demo (0)>> CLEARSELECT
So, I deleted the index and recreated (and rebuilt) them. Then I tried again
running
all the commands one right after another:
4 Demo (0)-> .X9,11,9,8,9,10,9,8
TIME
13:38:16 Aug 16 2007
SELECT GLPOST WITH CLIENTNO = "605"
33137 records selected to list 0.
TIME
13:38:21 Aug 16 2007
CLEARSELECT
TIME
13:38:21 Aug 16 2007
SELECT GLPOST WITH INDEX_2 = "0605]"
33137 records selected to list 0.
TIME
13:38:38 Aug 16 2007
CLEARSELECT
4 Demo (0)->
As you can see, the supposed index select is significantly slower than the
regular
select. Checking the file I get:
4 Demo (0)-> FILE.STAT GLPOST
13:40:07 Aug 16 2007
FILE MOD OV HTY ITEMS BYTES MNI/G MXI/G MNB/I MXB/I
GLPOST 20543 1494 0 1227419 113228292 1 64 55
137
------- ------- -------
22037 1227419 113228292
...so I don't think it is a file issue.
This appears to be a pretty significant problem. I didn't really notice this
during
the six months of testing because the machine was so fast, as is UD. But now,
in
production, we're getting some slowness the users are noticing.
Bill
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of
>[EMAIL PROTECTED]
>Sent: Thursday, August 16, 2007 12:39 PM
>To: [email protected]
>Subject: RE: {Blocked Content} RE: [U2] UD: Using indexes in UniQuery
>
>I knew the index dictionary was virtual - I was wondering if the
>clientno etc were maybe translates or something else that that the
>select query might use to invalidate the index. I think the
>only trouble
>we ever had with UD indices what that it wasn't actually built - but
>your list.index showed it as being built.
>
>Never really had to test if the index was used - it was always way
>faster. It would be interesting to know how long an un-indexed select
>would take on the two boxes.
>
>The only thing I've had to do with and index is delete and
>re-create it.
>Make sure you DELETE-INDEX GLPOST ALL, then make sure the X_GLPOST file
>has been removed. Then re-create and re-build the index -
>making sure no
>one is accessing the file at the time. I have seen an index that was
>created while the file was actively being updated do some strange
>things.
>
>hth
>Colin Alfke
>Calgary Canada
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
