Verity question

We have an app that is using verity to search docs and db.  What is the best process for speed when thinking about updating the index and doing the cfsearch.  There are thousands of records and will be a pretty substantial amount of traffic.  So far what I have read is the do a cflock around all cfsearch tags and an exclusive lock around the indexing (full and partial).  The index will be updated when records/docs have been updated.  Does anyone have any experience with this?  Is there a better way of doing this?  I am just worried about the cflock slowing everything down if there are a lot of people accessing it at the same time. Thanks! -Lori

you could schedule just the one index every 24 hrs in the quite hours instead of after each new record addition Stone, Lori wrote: ----- Excess quoted text cut - see Original Post for more -----

Yes, I planned on doing that also.  Unfortunately, the issue will still be the same as there are a number of users that will be using the system at all times of the day. -Lori you could schedule just the one index every 24 hrs in the quite hours instead of after each new record addition Stone, Lori wrote: > We have an app that is using verity to search docs and db.  What is the > best process for speed when thinking about updating the index and doing > the cfsearch.  There are thousands of records and will be a pretty > substantial amount of traffic.  So far what I have read is the do a > cflock around all cfsearch tags and an exclusive lock around the > indexing (full and partial).  The index will be updated when > records/docs have been updated.  Does anyone have any experience with > this?  Is there a better way of doing this?  I am just worried about the > cflock slowing everything down if there are a lot of people accessing it > at the same time. > > Thanks! > > -Lori > >

On Fri, Mar 28, 2008 at 8:44 AM, Stone, Lori <Lori.Stone@acqsolinc.com> wrote: > We have an app that is using verity to search docs and db.  What is the >  best process for speed when thinking about updating the index and doing >  the cfsearch.  There are thousands of records and will be a pretty >  substantial amount of traffic.  So far what I have read is the do a >  cflock around all cfsearch tags and an exclusive lock around the >  indexing (full and partial). Where did you read that? That should not be the case in CF7and higher. The index will be updated when >  records/docs have been updated.  Does anyone have any experience with >  this?  Is there a better way of doing this?  I am just worried about the >  cflock slowing everything down if there are a lot of people accessing it >  at the same time. Get rid of the cfdocs, and don't forget that cfindex allows for atomic updates. Ie, just because you change one thing, you don't have to nuke the entire collection. -- =========================================================================== Raymond Camden, Camden Media Email : ray@camdenfamily.com Blog : www.coldfusionjedi.com AOL IM : cfjedimaster Keep up to date with the community: http://www.coldfusionbloggers.org

Yes, I know you do not have to do the entire thing.  I was going to update individually as needed and do a full index once a day.  I am not sure what cfdocs you are referring to.  I just want to know the best way to update the verity collections without having other users hitting it at the same time.  Would it be better to just count on the individual updates and not worry about the full update?  I haven't used verity in a while.  I know I used to have problems with the collections getting corrupted which is why I wanted to do the full index every night. Thanks! -Lori On Fri, Mar 28, 2008 at 8:44 AM, Stone, Lori <Lori.Stone@acqsolinc.com> wrote: > We have an app that is using verity to search docs and db.  What is the >  best process for speed when thinking about updating the index and doing >  the cfsearch.  There are thousands of records and will be a pretty >  substantial amount of traffic.  So far what I have read is the do a >  cflock around all cfsearch tags and an exclusive lock around the >  indexing (full and partial). Where did you read that? That should not be the case in CF7and higher. The index will be updated when >  records/docs have been updated.  Does anyone have any experience with >  this?  Is there a better way of doing this?  I am just worried about the >  cflock slowing everything down if there are a lot of people accessing it >  at the same time. Get rid of the cfdocs, and don't forget that cfindex allows for atomic updates. Ie, just because you change one thing, you don't have to nuke the entire collection. -- ======================================================================== === Raymond Camden, Camden Media Email : ray@camdenfamily.com Blog : www.coldfusionjedi.com AOL IM : cfjedimaster Keep up to date with the community: http://www.coldfusionbloggers.org

Sorry, I meant get rid of the cflocks. You should not need them CF7 and higher. I'd get rid of the big update and just do individual, atomic updates. On Fri, Mar 28, 2008 at 12:11 PM, Stone, Lori <Lori.Stone@acqsolinc.com> wrote: ----- Excess quoted text cut - see Original Post for more ----- -- =========================================================================== Raymond Camden, Camden Media Email : ray@camdenfamily.com Blog : www.coldfusionjedi.com AOL IM : cfjedimaster Keep up to date with the community: http://www.coldfusionbloggers.org