Indexing is extremely slow!

[henryonpoint]

Looking at the Enterprise Data Flow Manager, it is taking forever to index new documents. The Extractor to Document Conversion Interchange Pool is running but shows 0 pending items for minutes at a time, then with show between 1-3 items and then they will push through quickly to the Enterprise update Distributor. In 12 hours is has processed 227 items. The schedule for both Enterprise extractor and Doc Conversion were lowered to every 20 seconds.

We have tried so many settings and have even tried rebuilding the index, but it still ran this slow...so we restored the indexes. We have documents that are over a week old that still are not showing in search. Eventually they show up, but this does not seem right.

We have 8 Partitions. There are no visible errors and the server is oversized and running well.

I have a feeling there is something I'm not looking at. Hopefully some experts here can help!

 

[henryonpoint]

Also...Livelink Version is 9.7.0.259

 

[appnair]

what is the count of rows in windexnotify?

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in

 

[henryonpoint]

Is this Appu Nair? If so, this is Henry Hernandez. Hey old friend! I hope you are doing well...and thanks for the help! I'd love to catch up offline.

The row count of windexnotify is 398690.

 

[appnair]

its me if you really don't want workflow to pass thru indexer you can copy that info to another place and truncate the table and just watch it from growing
livelink's index process gives priority to items in workflow before it will do the others.Also that could not be your problem as 9.7.1 code will have indexed new ones
first before it takes on old stuff.My guess is probably your install is it SQlserver or oracle?I have my doubts on another table ....

BTW Henry call me if you need to

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in

 

[henryonpoint]

Thanks Appu. I ran an index verification. It came back with 17k items to be re-indexed. It seems to be back on track now, but the indexer still runs at about 1-2 object per minute through the Extractor-Doc Conversion-UpdateDistributor Data flow process. Does that seem right? That means the 17k items could take 10 days...plus any items being added during that time.

 

[appnair]

most companies don't care for workflow items to be indexed so I usually truncate the table.Then I put certain things to be excluded it is just common sense that livelink or no program can FT index a access database.So use common sense and put up extractor exclusions.If you run a group by of all the mime types you probably can find all the stuff that acnnot be FT indexed.If users add anything new then the re-indexing stops in favor of the LIFO algorithm.You are getting some problem in your uindexing usually about 500 items can be indexed in 2 minutes almost.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in