You are viewing limited content. For full access, please sign in.

Question

Question

Import Agent 10 and CPU Utilization

asked on September 8, 2016

We recently moved Laserfiche 10 to a new server, and upgraded Import Agent from 9 to 10, also moving the app to the new machine.  The new server has two Zeon E5-2626 CPUs, 2.4 GhZ, 24 cores total, and 32 GB RAM, solid state drives.  Lots of processing power.

We have measured Import Agent generally taking 3-4% CPU utilization, then spiking to around 15% five times a minute on a regular interval. I assume this is its polling interval.  This is during times when no one is sending anything to it.  I understand that it will be doing a range of OCR and image processing operations when it does get work. However, it seems like it is consuming an awful lot of CPU resources when it is just loafing along.  

Can someone offer background on why this might be happening?  And are there settings that can make IA less aggressive?

 

 

0 0

Answer

SELECTED ANSWER
replied on September 13, 2016

And the spiking is probably caused the monitoring files. Since you have about 100 sessions, it means Import Agent will monitor about 100 directory every one minute. I guess it is expected. But you can try to increase the interval to reduce the spiking. See the configuration in the below picture. 

Another thing is that, if some of your 100 profiles are expected to work at specified time, we suggest enable the schedule instead of continuously import. The option is on the profile dialog.

 

 

 

 

0 0

Replies

replied on September 8, 2016

I configured a basic IA profile and I'm not seeing any kind of CPU spikes. We would appreciate if you could open a support case with memory dumps of ImportAgentService.exe during one of these spikes. You can get a dump easily with Process Explorer.  Right click on ImportAgentService.exem choose Create Dump->Create Full Dump and choose a destination. If possible, get more than one dump.

0 0
replied on September 9, 2016

Thanks, Rob.  I'll post the results back here once we get a handle on it.

0 0
replied on September 11, 2016

Hi Bill,

Can you confirm whether there is at least one enabled? If all profiles are disabled, there is a bug which causes CPU using about 13%-15%. The workaround is to enable at least one profile.

 

Thanks,

Qinmei

0 0
replied on September 12, 2016

Hi Qinmei -

It must be something else - we have about 100 sessions, and they are all enabled. As an experiment, I disabled one profile and then re-enabled a profile, restarting both times, but it's still spiking.

Bill

 

0 0
replied on September 13, 2016

Hi Bill,

Could you please try to decrease the import thread count? Please navigate to HKLM\Software\Laserfiche\Import Agent\Settings and add a new string value "ImportThreadCount". By default, the value is equal to core count of the machine. Try a smaller value!

 

Thanks,

Huazhen

0 0
SELECTED ANSWER
replied on September 13, 2016

And the spiking is probably caused the monitoring files. Since you have about 100 sessions, it means Import Agent will monitor about 100 directory every one minute. I guess it is expected. But you can try to increase the interval to reduce the spiking. See the configuration in the below picture. 

Another thing is that, if some of your 100 profiles are expected to work at specified time, we suggest enable the schedule instead of continuously import. The option is on the profile dialog.

 

 

 

 

0 0
replied on September 13, 2016

Thanks, Gentlemen -

The spikes were definitely related to the polling interval.  When I set this to :15, the spikes changed from 5X/minute to 4X/minute. Changing the thread count to 16 (from the default of 32) also helped.  Previously, the CPU utilization ran up to the 15-18% range, across 6 processors, with an overall level of 6%.  Going to 16 threads dropped this to 9%, across 2 processors, with an overall level of 2.5%.  Since we can also use DCC for the OCR part (nice addition) all of this will help keep things at reasonable levels.

Thanks again -

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.