Problem/Question
When you configure RipEngines in the Ergosoft ControlCenter, page "RIP & Programs" you can set the number of threads to be used per RipEngine.
And questions like the following can come up:
What is the meaning of this setting?
Can I influence the ripping speed with this setting?
How can I activate multi-threading?
How can I configure multi-core use?
Solution/Work-Around
The RipEngines can do multi-threading for color channels, always per job.
- When your job has 4 color channels (light inks are in the same color channels as the standard ink), the maximum ripping speed is reached with 4 Threads per RipEngine.
- When your job, for example, has 6 color channels and you allow 4 threads per RipEngine, the processing of the color channels is done in 2 sections:
- the first section with 4 color channels
- and the second section with 2 color channels.
- In this example with 6 color channels, 3 or 4 or 5 threads per RipEngine result in the same ripping speed.
Using several RipEngines at the same time / ripping several jobs simultaneously.
- Each RipEngine will use the same number of cores.
- Windows controls the usage / splitting of cores.
- When the CPU has less cores than the active RipEngines together require, the cores will be shared so that several threads (of the same or different RipEngines) run on the same core.
Example:
- Conditions:
- Precondition: No other software is used at the same time
- 8 physical core CPU
- 1 printer
- Process 2 jobs, each in CMYK (4 color channels)
- Calculation:
- 2 jobs simultaneously = 2 active RipEngines
- 4 color channels = 4 threads
- Cores needed: 2x4 = 8
- Result:
- There are going to be eight (2x4=8) active parallel threads assigned to one (1) physical core each.
- Having 2 RipEngines at 4 threads each activated allows you to pre-process the follower job while processing/printing the forerunner.
- Side note:
- In this situation one job processed will still use only 4 threads => physical cores.
- Do not change the threads to 8. It won’t improve anything on a 4 colors output device.
Not enough cores to allow one physical core per thread:
- In this case, you have to test all reasonable combinations of threads per RipEngines, considering the number of active RipEngines, and measure the ripping speed.
- Example:
- CPU with 4 cores
- 2 active RipEngines
- 4 color channels
- Reasonable settings for threads per RipEngine:
- 4: Ripping is done in 1 section, cores are shared between RipEngines
- 2: Ripping is done in 2 sections, cores do not need to be shared between RipEngines
Related Articles & Links