COURSE NAVIGATION

Tuning performance and memory settings

The biggest single factor that influences performance is the number of pixels that the image consists off. The larger the number of pixels, the more time it will take to process the image. Therefore, it is good to check your resample settings, if they are set correctly for your workflow. Read “To resample or not to resample“.

You can also set a limit on the size of images, so that individual images are not holding up your production. See screenshot below of those settings, which can be found in SIZE settings.

Size limitations

(MPixel = Mega-pixel or 1 million pixels).

System requirements and OS

Read this: System requirements, throughput and performance.

Note that besides the obvious (processor speed and RAM), I/O performance is very important too. (speed of writing to and reading from hard-drive). SSD drives are great for performance. Especially if you work in virtual environments, make sure the I/O speed is good. The same goes for network speed if you use folders on the network.

Concurrent image processes

Claro can process up to 4 images simultaneously. The number of concurrent processes can be set during installation, or by editing the jClaro.conf file. Please note that it does not make sense to configure a number of concurrent processes that is higher than the number of processor-cores that are available. That will just slow things down. Also, make sure that there is sufficient RAM available in the machine to support the number of concurrent processes. 2GB per concurrent process, plus 2GB additional for the OS is a good guideline. I.e., on a quad core server, with 12GB RAM, you can safely configure 4 concurrent processes and 2GB RAM per process.

Configuring the number of concurrent processes and memory

To set these using the installer, read this: Installation. Note that you can run the installer again, and install over the existing installation without losing any of your configuration. So it is a valid way of changing those settings.

! Please note: if you configure >1 concurrent image process, the memory for the main process can be limited to 1GB, as the main process will not be processing images, but rather just be scheduling jobs to the concurrent processes. But, if you configure only 1 concurrent process, the main process will be processing the images. In that case, the main process needs at least 2 GB of RAM.

To change this by editing the jClaro.conf file:

This file can be found in the installation directory:

../Elpical Claro/conf/jClaro.conf

Open this file in your favourite text-editor. Locate these lines:

# Concurrent image processes and max memory/process (in MB)

wrapper.java.additional.6=-Dcom.elpical.concurrent=4

wrapper.java.additional.7=-Dcom.elpical.concurrent_maxmemory=2048

AND this one:

# Maximum Java Heap Size (in MB)

wrapper.java.maxmemory=1024

Change the values and save the file. A restart of the Claro service is required for the changes to take effect.

Print Friendly

ELEARNING SEARCH

Questions?

ELPICAL

JOHN DE JONG

Phone +31 (0) 313 633 156
E-Mail [email protected]
Skype ELPICALJOHN
Sorry, it seems that your browser is outdated. You can quickly install an update below.
Download Here: