Home › Forums › implementation › Implementation discussion ›

Efficiency of docload

Submitted by Guest on Sat, 23/11/2013 - 06:11
in

I have just set up the automatic loading of investigation results and I have docload running every 10 minutes. I have noticed that although the system is idling along (with no results being loaded) docload does a fairly heavy hit on the system - see below - it uses around 30% of the cpu for 9 seconds.

I appreciate that to fire up a java app takes a bit of time, but this seems a large cost to wake up, look in the source directory, find no files, and exit.

I am considering putting logic in the batch file to look and see if there are any new files in the folder, and if not exit immediately without firing up docload.

Has anyone else looked at this problem?

Regards, Tim G

‹ Is it possible to find out who requested a report? Investigation template -type? ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Efficiency of docload

Submitted by tanderson on Sat, 23/11/2013 - 17:46.

When docload starts, it initialises itself using the <OPENVPMS_HOME>/conf/applicationContext.xml configuration file.

I haven't profiled it, but I suspect much of the time is taken initialising the archetypeService, which loads all of the archetype descriptors.

If you are running docload with the -byname argument, there may also be a performance hit, if you have a large no. of document acts with no corresponding documents.

-Tim A

Re: Efficiency of docload

Submitted by tgething (not verified) on Sun, 24/11/2013 - 11:11.

No Tim - I am running: docload --byid --source c:\TestRes\Results --dest c:\TestRes\Loaded

Humm - I might try constraining type just to investigations. 

Switched to the following - but no improvement.
docload --byid --type act.patientInvestigation --source c:\TestRes\Results --dest c:\TestRes\Loaded

Regards, Tim G

Syndicate content