The Usage report section requires a Usage report license and is only available for user accounts with Administrator status. This section allows you to create customized reports on certain usage statistics such as disk usage and project count. These reports can be drafted for a certain date range, allowing you to monitor resource usage over defined periods of time.

The Saved reports section lists previously-generated usage reports that have been saved by the user (Figure 1). These can be used to review former reports generated. Click on the button to delete any saved reports.

To generate a usage report, go to the Generate report section. Select the following:

• The metric you would like reported (Report)

• How you would like the information grouped (For each)

• The Date range to be reported

For instance, Figure 2 shows the creation of a disk usage report for each project within a custom date range.

After selecting your options, click the Generate report button. The usage report will be displayed at the bottom of the page as a table (Figure 3). Click on the Save report link at the lower left corner of the table to save the report. To download the report as a tab-delimited text file, click the Download link at the lower right corner of the table.

Additional Assistance

If you need additional assistance, please visit our support page to submit a help ticket or find phone numbers for regional support.

The System queue page gives you the list of system-related tasks performed on your Partek Flow server (Figure 1). These tasks generally benefit all the users of the server. They include, but are not restricted to, downloading annotation databases and building aligner indexes.

Filter to a specific task by entering keywords in the Task search box. Use the drop-down menu under the corresponding column header to filter tasks to specific users/date ranges and statuses. The progress of ongoing system tasks is displayed as a bar in the Status column. Cancel any ongoing task by clicking the button.

Additional Assistance

If you need additional assistance, please visit our support page to submit a help ticket or find phone numbers for regional support.

Partek Flow gives you the ability to evaluate and modify the hardware resources available for analysis, track system tasks, and, with the purchase of a Usage report license, generate usage reports for your Partek Flow instance. These options are located in the Settings menu. This document will describe the following sections:

• System Queue

• System Resources

• Usage Report

Additional Assistance

If you need additional assistance, please visit our support page to submit a help ticket or find phone numbers for regional support.

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

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 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.

The Active workers table lists one active worker node per row (an example with a single worker is shown in Figure 1) 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 stops a worker while selecting starts a worker (Figure 2)

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 3 shows an example with five active workers.

Additional Assistance

If you need additional assistance, please visit our support page to submit a help ticket or find phone numbers for regional support.