Hello all,
Great work on the 14. release, jobs engine and concurrency are amazing additions. Just two quick questions:
Moving configuration file from the previous version, the only addition is under General configuration of Orthanc correct?
// Maximum number of processing jobs that are simultanously running
// at any given time. A value of “0” indicates to use all the
// available CPU logical cores. To emulate Orthanc <= 1.3.2, set
// this value to “1”.
“ConcurrentJobs” : 0,
For the concurrent jobs, with concurrent sending. You mentioned concurrency in DICOM sending, is there concurrency in Peer also?
Thanks for all the work!!
Hello Bryan,
Thanks for the positive feedback!
The introduction of new configuration options is documented in the NEWS file (that contains the release notes):
https://bitbucket.org/sjodogne/orthanc/src/default/NEWS
You can also check the precise differences between successive versions of the configuration file by cloning the source repository, then using the following Mercurial command line:
hg diff Resources/Configuration.json -r Orthanc-1.3.2…Orthanc-1.4.0
There are actually 3 new configuration options in 1.4.0, that all deal with the new jobs engine: “ConcurrentJobs”, “SynchronousCMove”, and “JobsHistorySize”. The documentation of these options is as always embedded in the default configuration file:
https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Configuration.json
To answer the second part of your question, yes, concurrent sending to peers is also handled. Actually, both DICOM and peer transfers are considered similarly as jobs.
You can see a status of all the jobs by opening your Orthanc Explorer at the following location:
http://localhost:8042/app/explorer.html#jobs
HTH,
Sébastien-