IDOL Indexing Task for 150 K MB 4.6.2 assets is taking more time

Hi,

We have done MB 8.1 Dev environment refresh with production 4.6.2 data

There are around 150 K assets in our production 4.6.2 MediaBin.

i'hve invoked IDOL one time indexing house keeping task.

it took almost 4 hours to index 6500 assets. i wonder how much time it will take to finish indexing/extracting metadata for remaining assets. for every few minutes i am checking the IDOL to see how many assets indexed using the below URL. Its updating after every 100 records.

http://localhost:9000/action=getstatus

Is the slowness in indexing is expected behaviuor for initial indexing ?or i am i doing some thing wrong?

Please suggest.

Thanks,
Shravan

Find more posts tagged with

Comments

rmedida

The IDOL indexing will happen in batches of 100. Yes, it will take time based on the number of Metadata fields set in IDOL configuration file.

Shravan

Thank you. in cofig file exactly which place we will set or set by default?

i could see in two places various metadata fields were set

Shravan

It took 20 hours to process 14K documents. still 120 K left.

we have to waiit alsmost till 4 days to finish this IDOL index processing?

any suggestions to improve the processing speed? is it the same case for everyone?

rmedida

Standalone IDOL indexing speed depends on many factors (ex. Disk read & write, CPUs). Is the MediaBin system actively being used by business users?

Shravan

its a dev environment. no one is using it.

here is the config - 8 GB RAM, ample diskspace 2 CPUS. not sure if i need to modify any settings so that 2 CPUS will be allocated to server.

Shravan

i could see that several kvoop.exe processes are running which are causing 100 % CPU utilization.

Are these related to IDOL indexing?

rmedida

Yes, its KeyView engine that populates the IDOL Summery metadata from MSOffice/PDF documents.

Shravan

server seems to be struck, due to heavy load . i have to force restart. if i restart MB server service, does the index happens after reboot automatically, or we need to again run the scheduler.

if we run the scheduler, whether indexing agains start from begiinning or it will extract content/ index for only non - indexed ones. please confirm.

rmedida

IDOL indexing will resume after the MediaBin server service restart.

You can check the Performance tab of Windows task manager and consider upgrading the hardware if it is really system resources issue.

Shravan

i have to kill kvoop.exe process manually and restart the server most of the times to fix the slowness issue.

This kevwiew process (two or more) is some how running for every 2 hours or so and causing 100 % CPU utilization which is causing server to slow down or hang.

even though the IDOL shceduler is off and indexing is done for older assets , i wonder why this process still runs some time. i don' see any issue with hardware configurations since it is as per requirements/congifuration document provided by HP.

rmedida

Any file uploads at the time of Kvoop running?

Shravan

No Ravi. since its dev server, i am the only one who has access.

i was idle for few hours then logged into MB and noticed that login time is taking more time.

then i logged into our app server box, which was very very slow doue to Kvoop process took cpu time. i was some how killed those processes and immediately noticed that server is beghaving normally.

tposton

What is the database load looking like? Is SQL server busy? Does it have any hung processes? Do you have a large number of PDF or Office documents?