Pat -
I saw a posting of yours elsewhere dated January of 06 regarding slow
verity indexing. After searching your name, I found this cfaussie
thread.
I have encountered exactly the same cfindex problem. It takes waaay
too long. I've been looking for the cause, but have developed a
response.
I'm still confused. You compare an update of 1 row to an update of 100
rows. Normally cfindex is slower when you compare the following:
You have 100 rows to update.
Option A: Loop over each row and insert one at a time.
Option B: Insert all at once as a query.
Does this describe what you are
I've done a few presentations on Verity in the past. CF7 had a major
update, hence the reason there are a lot of new features in CF7 in
terms on Verity. As for this particular point, I guess I woul dhave
always assumed that one update versus N would be quicker.
On 5/22/07, Pat Branley [EMAIL
On 5/22/07, Pat Branley [EMAIL PROTECTED] wrote:
So do you know of a 'best practice' methodology for dealing with
verity indexing of database content ?
I'm not aware of such a document. I know that when I teach Verity I
talk about the importance of keeping your index in sync with your db.
So
when you say not super fast, but fast how long would you expect a 1
record index to take ? on our servers this can be 10 seconds and
upwards per CFINDEX call. hence the need to call cfindex via a
schedule.
but if i do the same cfindex call with 100 rows it may only take 20-30
seconds.
this
