Partek Flow Documentation

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel2
minLevel2
excludeAdditional Assistance

 

The System resources page gives users information about the hardware resources available for use in their Partek Flow server.

 

 
Numbered figure captions
SubtitleTextSystem resources page
AnchorNameSystem resources page

Image Modified

The Queue status section indicates the number tasks currently running as well as the number of waiting tasks. These include tasks that are waiting for system resources to be available or for an upstream task to complete. Queue will empty by gives an estimated time of completion for all queued tasks. Click on the Image Added button to display queued tasks.

 The Licensing section summarizes the number of Available cores licenses and Available worker licenses. Contact your Account Manager to obtain additional core or worker licenses.

 

Section Heading

Section headings should use level 2 heading, while the content of the section should use paragraph (which is the default). You can choose the style in the first dropdown in toolbar.

 

 The Active workers table lists one active worker node per row (an example with a single worker is shown in Figure 2) and contains performance metrics for worker processes and server processes. The columns provide the following information: 

  • Name: worker’s identifier (IP address or name)

  • CPU usage: the computational load of the worker process

  • Memory usage: the memory usage of the worker process

  • Machine capacity: indicates the number of cores and amount of RAM available to the worker

  • Uptime: the duration that the worker has been running

  • Type: the type of worker (described below)

  • Actions: selecting the Image Added stops a worker while selecting Image Added starts a worker (Figure 2)


 

 

 
Numbered figure captions
SubtitleTextStarting a worker
AnchorNameStarting a worker

000386_2016_02_23.pngImage Added

Partek Flow supports two types of workers: Partek Flow is installed on the server while those labeled worker run on a remote machine. When the server is configured to accept work, its type is changed to internal to differentiate it from other workers. Multiple workers can be deployed to handle computationally-intensive tasks or to help alleviate a long queue of tasks. Figure 4 shows an example with five active workers.

 

 
Numbered figure captions
SubtitleTextResources management page displaying five active workers
AnchorNameActive workers

Image Added

 

Additional assistance

 

Rate Macro
allowUsersfalse