Subject | Incremental Search verrrry sloooowww. |
---|---|
Author | garthtissington |
Post date | 2003-12-02T18:57:42Z |
Hi,
I'm new to IBObjects and Firebird so I appologize in advance if I'm
missing something obvious.
I'm using Firebird & IBObjects. I'm evaluating Incremental search
from IBObjects and Infopower.
I built a sample app with two scenarios:
a) IB_Query + IB_IncrementalSearch
b) IBO_Query + TwwIncrementSearch
That sample data has over 50,000 rows. It is running in Firebird
superserver mode with the local protocal and a physical db on the
same machine (i.e. no drive mapping)
When I first tested this scenario a) was instantaneous and scenario
b) had a latency of about 6 seconds on the first search but all
subsequent searches were nearly instantaneous
I don't know what changed but now scenario a) has a latency of
nearly 30 seconds while a dialog pops up say "Fetching record (n) of
50000" on the first search, subsequent searches are fine; scenario
b) is exactly the same as before.
The database is indexed on the field being searched.
Now the questions....
1) Any idea why the IB_Query configuration should slow down from
sterllar performance to abysmal. What am I doing wrong?
2) Any idea who I can reduce this latency in the Infor Power
Compontnest. It is a TDataset with an index. It really shouldnlt
need to scan the entire table to do incremtnal search.
All suggestions very much approceiated.
Garth
I'm new to IBObjects and Firebird so I appologize in advance if I'm
missing something obvious.
I'm using Firebird & IBObjects. I'm evaluating Incremental search
from IBObjects and Infopower.
I built a sample app with two scenarios:
a) IB_Query + IB_IncrementalSearch
b) IBO_Query + TwwIncrementSearch
That sample data has over 50,000 rows. It is running in Firebird
superserver mode with the local protocal and a physical db on the
same machine (i.e. no drive mapping)
When I first tested this scenario a) was instantaneous and scenario
b) had a latency of about 6 seconds on the first search but all
subsequent searches were nearly instantaneous
I don't know what changed but now scenario a) has a latency of
nearly 30 seconds while a dialog pops up say "Fetching record (n) of
50000" on the first search, subsequent searches are fine; scenario
b) is exactly the same as before.
The database is indexed on the field being searched.
Now the questions....
1) Any idea why the IB_Query configuration should slow down from
sterllar performance to abysmal. What am I doing wrong?
2) Any idea who I can reduce this latency in the Infor Power
Compontnest. It is a TDataset with an index. It really shouldnlt
need to scan the entire table to do incremtnal search.
All suggestions very much approceiated.
Garth