This problem is on an shared MX7 server at intermedia.net.

When updating a custom search record, <cfindex> takes so long (25 seconds,
minimum) that subsequent <cfoutput> tags often timeout.

On my development server (older machine running MX6.1), the same index update
takes 2 or 3 seconds.

Interestingly, when I update ten records at once, it only takes a second
longer.

There doesn't seem to be any info on this problem, and the folks at
intermedia, while well-intended, aren't pursuing this with gusto.

I've gone so far as to create a database table for indexing requests, queueing
the requests for scheduled indexing, so that users don't hang and get errors
when they update data. Even this isn't working very well, as some queued
entries are taking many hours befores successfully indexing!

There's a test script at [url]http://www.uwri.org/v2alpha/testindexupdate.cfm[/url]. It
displays all information about it's operation, and can be expected to timeout
about half the time.

Any ideas out there??

Thanks,

Don