CPU running at 99% with DCC Scheduler

asked on October 28, 2015

Hi,

There are so many posts about this. I thought sharing mine would be good too. I have DCC installed on a clients LF Server. They are using Import agent and i am not using the OCR feature on there as it takes longer to import the documents. The scheduler is set to run at 5PM everyday and it takes 1000 Documents. It seems like those documents never completes and then if i go into Task Manager i can see 4 instances running of LF OCR Engine which causes the Flatline of 99% on the LF server making it very difficult to work on the server and users experience issues.

What is the best practise for the DCC?

The server specs: (this is a virtual server)

0 0

replied on October 28, 2015

This is expected behavior for OCR. DCC has 2 components: the scheduler and the workers. The scheduler is in charge of distributing the OCR tasks to the workers. The workers are doing the actual OCR, which is fairly CPU-intensive. This architecture is intended to distribute the load to a set of machines and away from a server.

The scheduler can be set up to perform OCR jobs as well, but that is not the recommended configuration. The scheduler is fairly low impact and can run on a server. The worker nodes will go for OCR speed, so they'll use as much of the processor as needed. For each worker, you can limit the number of CPUs available for OCR jobs. In your case, if you're using this server as both a scheduler and a worker, I would limit the number of CPUs allowed for OCR to 1.

0 0

Question

Question

CPU running at 99% with DCC Scheduler

Replies

Sign in to reply to this post.