HIPO configuration

At times, Matrix must perform highly intensive processes to perform functions such as cascading permissions or setting workflow. In these cases, Highly Intensive Processing Object (HIPO) jobs are used to perform these actions, allowing the user to view the progress of a task as it is being performed.

Squiz server configuration

For large systems, HIPO jobs can take a long time to complete. The Squiz server allows you to speed up the system’s processing by running these HIPO jobs directly on its server while still showing the progress of the task to the user.

You must have the Squiz server extension installed on your Matrix instance before you can enable it on this screen and configure the fields. Once installed and configured correctly, enable the Run on Squiz server option in this section.

Status check threshold

The number of seconds that the system should wait before querying the server to the job’s status. The below values can only be edited through the data/private/conf/squiz_server.inc file and must be configured if run on a Squiz server is enabled.

System root

The location where the Squiz server was installed.

System ID

The unique identifier for the Matrix system. This ID identifies the specific Matrix system on the Squiz server, managing several Matrix systems. This ID can be found in the server.conf file in the Squiz server directory.

Domain

The domain used to connect to the Squiz server. If the Squiz server runs on the same server as Matrix, this field should be set to localhost.

Port

The port on which the Squiz server is listening.

Thresholds

This section allows you to configure the thresholds for the number of different types of HIPO jobs that can be run simultaneously.

If a threshold is set to a low value such as 1, a user will always see a HIPO job progress started for that action. If you have a powerful server, you can configure your system so that less intensive jobs run immediately and not as a HIPO job by setting the threshold higher.

If the number of assets processed by a HIPO job is less than the threshold entered, a HIPO job will not appear within the editing screen.

If the number of assets is more than the threshold, a HIPO job will appear, but it will only be refreshed once the set number of assets has been processed.

For example, if the edit status threshold is set to 20 and you change the status for 19 assets, no HIPO job will appear as it is below the threshold. If you change the status for 100 assets, a HIPO job will appear but will only be refreshed five times (once for every 20 assets it processes).

Freestyle threshold

The percentage of the total number of HIPO processes. For example, say you set this field as 80%. You then have a job running that uses 50% of a particular set threshold and another job that also uses 50% of another set threshold, giving a total of 100%. Because you have exceeded the freestyle threshold of 80%, the job will be run as a HIPO.

This field can have a value of over 100%.
Lookups updating threshold

The number of assets that can be updated by a user updating a URL, URLs, or applying a design without a HIPO job being spawned.

Workflow schemas threshold

The number of assets that can be updated by a user cascading workflow schema without a HIPO job being spawned.

Permissions threshold

The number of assets that can be updated by a user cascading permissions without a HIPO job being spawned.

Trigger execution threshold

The number of triggers that can be executed without a HIPO job being spawned.

Edit status threshold

The number of assets whose status can be changed without a HIPO job being spawned.

Acquire lock threshold

The number of assets a user can lock without a HIPO job being spawned.

Edit metadata threshold

The number of assets that can be updated by a user cascading metadata without a HIPO job being spawned.

Purge trash threshold

The number of assets a user can purge from the trash without a HIPO job being spawned.

Edit tag threshold

The number of tags that can be changed without a HIPO job being spawned.

Metadata regeneration threshold

Threshold for the total number of assets that can be updated by a user regenerating metadata without a HIPO job being spawned.

Clear cache threshold

The number of assets that can have their cached cleared by a user without a HIPO job being spawned.

Report regeneration threshold

The number of assets that a report job can process without a HIPO job being spawned.

File import threshold

The number of file assets that can be created when performing a file import without a HIPO job being spawned.

© 2015- Squiz Pty Ltd