User Tools

Site Tools


system:processes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
system:processes [2021/02/07 16:37] benjaminsystem:processes [2024/01/28 10:26] (current) benjamin
Line 1: Line 1:
 ====== Process overview ====== ====== Process overview ======
  
-{{gallery>:system:process_model_1.jpg?400x400&1500X1500&lightbox}}+{{gallery>:system:process_model_1.jpg?400x150&1200X1200&lightbox}}
  
 ==== General Information ==== ==== General Information ====
Line 21: Line 21:
   * when rest_service is NOT installed, it fulfills the job of rest_service   * when rest_service is NOT installed, it fulfills the job of rest_service
  
-{{gallery>:system:process_with_transcode.png?900x900&1500X1500&lightbox}}+{{gallery>:system:process_with_transcode.png?900x150&1200X1200&lightbox}}
  
 In this picture, we see ffastrans.exe on a standalone host, not installed as service. ffastrans.exe took care about starting exe_manager which again started different sub-processes, e.g. def_runner.a3x and processors.a3x In this picture, we see ffastrans.exe on a standalone host, not installed as service. ffastrans.exe took care about starting exe_manager which again started different sub-processes, e.g. def_runner.a3x and processors.a3x
Line 30: Line 30:
   * provide http API service   * provide http API service
  
-{{gallery>:system:process_as_service.png?900x900&1500X1500&lightbox}}+{{gallery>:system:process_as_service.png?1200x150&1200X1200&lightbox}}
  
-In this picutre, we see that rest_service.exe took care about starting exe_manager.+In this picture, we see that rest_service.exe took care about starting exe_manager.
  
  
Line 56: Line 56:
 def_runner.a3x is started by exe_manager in case there are any active workflows that need watching for new files. def_runner.a3x is started by exe_manager in case there are any active workflows that need watching for new files.
  
-{{gallery>:system:process_base.png?900x900&1500X1500&lightbox}}+{{gallery>:system:process_base.png?1200x150&1200X1200&lightbox}}
  
 In this picture, we see that exe_manager started a sub-process that is also called exe_manager but when looking at the "command line", we see that one of the exe_manager sub-processes takes care about def_runner.a3x In this picture, we see that exe_manager started a sub-process that is also called exe_manager but when looking at the "command line", we see that one of the exe_manager sub-processes takes care about def_runner.a3x
Line 76: Line 76:
 Example for 4 max active jobs on 1 host, 2 hosts with 2 max active jobs or 4 hosts with 1 max active job: Example for 4 max active jobs on 1 host, 2 hosts with 2 max active jobs or 4 hosts with 1 max active job:
 \\ \\
-{{gallery>:system:jobs_priority.jpg?600x600&1200X1200&lightbox}}+{{gallery>:system:jobs_priority.jpg?700x350&1200X1200&lightbox}}
  
 ==== Job Ticket Management ==== ==== Job Ticket Management ====
  
-{{gallery>:system:processes_tickets.png?400x400&800X800&lightbox}}+{{gallery>:system:processes_tickets.png?700x350&800X800&lightbox}}
  
 This picture shows how the different processes work with Job Tickets. This picture shows how the different processes work with Job Tickets.
system/processes.1612715820.txt.gz · Last modified: 2021/02/07 16:37 by benjamin

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki