Subject: | |
From: | |
Reply To: | |
Date: | Tue, 20 Feb 1996 06:31:35 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Lilia Kotchetkova wrote:
>
> Those of you who uses Omnidex indexing software with Image database, can
> you tell whether enabling database for Third Party Indexing affects
> performance (measured or percieved)?
Lilia,
Regardless of which TPI product use, there will be a performance hit.
At a bare minimum there is one additional call between your DB...
call and IMAGE. Depending on the application, often it will only
be a measureable hit, and not perceived.
The DBPUT, DBDELETE, and DBUPDATE calls will take longer because you
are maintaining an index structure of some kind. However, this should
increase your retrievals when you are either doing a keyworded retrieval
or a partial key/range retrieval.
The fastest way to retrieve data is with the full key (actually knowing
the exact location of the record is faster, but this is what IMAGE keeps
up for you with the full key). If you have the full key value, then
use this type of retrieval. If you need keyword, then use it. IF
partial, use it. However, *never* use a key type just because it's
new or neat. Choose your types carefully and then use them properly.
This will generally provide you with acceptable performance at update
time, because of your gain at retrieval time.
Larry Boyd <[log in to unmask]>
"Each problem solved creates the opportunity to solve the next problem
that the last solution created." - Richard Pascale
(These opinions are my own and not those of Hewlett-Packard.)
|
|
|