General pointers and tuning tips

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Maintenance and administration > Monitoring > Bizagi Diagnostics > Using Bizagi Diagnostics >

General pointers and tuning tips

Overview

When monitoring and interpreting results in Bizagi Diagnostics, make sure you consider the following general pointers and tuning tips.

For introductory information about how to use Bizagi Diagnostics, refer to Using Bizagi Diagnostics.

 

 

General pointers

Consider the aspects which are part of underlying concepts in Bizagi regarding how it optimizes its operation.

 

1. Application startup or restart presents different response times.

Keep in mind that whenever Bizagi Engine is starting up (or has been restarted from its Web server), it will load a significant amount of resources.

This means that the Apdex indicator may show a slower response time whenever Bizagi Engine is initializing, and it could be often considered as normal behavior.

 

2. Recycling application resources.

Based on the above premise, note that you may watch after and configure adequately how often are the resources recycled by your Web server (e.g settings regarding pool cycling in the IIS), in order to achieve an optimal configuration where Bizagi Engine resource recycling or restart does not affect significantly your operations.

 

 

Tuning tips

Consider the following tips and optimization parameters.

 

1. Allocated memory for Bizagi Diagnostics.

For Bizagi Engine projects which process a really large amount of cases and activities on a daily basis (implies large volumes of information in logs), you may modify the memory allocated that Bizagi Diagnostics uses.

To do so, open the configuration file for the Diagnostics executable application which is located as C:\BizagiDiagnosticsTool\Bizagi.Diagnostics.Service\Bizagi.Diagnostics.Service.exe.config.

 

Modify the value for the ELK_Xmx (maximum) key which uses a default memory of 2147483648 bytes (2GB) according to your criteria and server's characteristics.

 

Diagnostics_config3

 

2. Filter the events that are logged, or when to do so.

Recall that by accessing the Settings options in the Bizagi Diagnostics web application, you may define which Bizagi server events are recorded by logs, by all components of every Bizagi Engine server.

Turn off those you do not identify as relevant for your needs, or define a threshold (in milliseconds) that limits when to record such events (it will set that these are to be recorded only when exceeding the threshold duration):

 

Diagnostics_app_settings

 

After changing a setting, ensure you click Update.

Use the following table as a reference regarding the list of Bizagi server events.

 

BIZAGI SERVER EVENT

DESCRIPTION

Library rules execution

Applies to whenever library rules are executed by Bizagi (i.e, those which are highly reused by being well-defined functions that receive inputs and outputs).

Web requests

Applies to requests that are solely web requests (HTTP).

Activate workitem

Applies to whenever a new BPMN shape instance is made available by the logic behind the workflow.

BPMN shape instance includes activities, sub-processes, events or gateways.

External service call

Applies to whenever there is an interface invoked via the WS Connector.

Case processing (save and next)

Applies requests that are solely produced upon having the user click Next or click Save in an activity's user interface.

Jobs processing

Applies to whenever custom jobs are run.

Custom traces

Applies to tracing features included by logic (i.e, scripting expressions using the CHelper.trace() method).

Business rules

Applies to whenever rules are executed by Bizagi (e.g, scripting expressions).

Build forms

Applies to whenever user activities are loaded, having its form displayed.

SQL Queries

Applies to run SQL queries which are part of any request.

 

3. Define the best event recollection and storage system to employ.

In addition to the above, recall that for each Bizagi Work portal or Scheduler service, you may define if they record server events and further options on how they do so (e.g, which storage is used).

These options are helpful according to how busy your system is, or which options you can consider best.

For instance and when using a File system, you should always ensure the rate or filesize under which files are being created is appropriate for your environment.

To view all available options to use these keys, or use additional possibilities regarding how to record and collect server events, refer to Advanced options when recording server events.