NetRule 4.3 Release Notes

NetRule 4.3 includes features enabling you to

1. track disk storage space on servers
2. incorporate user wait time while waiting for responses from multi-tier jobs -- this is a feature in the MT module only.

It also includes efficiency improvements and bug fixes.

Users with current maintenance agreements can download the release from www.analyticalengines.com.

Release Notes on tracking server disk storage --

For scenarios where accumulation of disk storage is of interest, NetRule calculates the rate by which server storage is being filled and the number of storage hours remain at that rate.

For a simple example of this new feature, open mfg_voip.net.

1. From the computer profile list, you can select servers and input on their profiles storage size in terms of gigabytes per disk.
2. From the job profile list, you can select the job profiles that are executed on the servers. Enter on the job profiles the numbers of additional bytes stored each time a job profile is run.
3. After evaluating, you will see on each computer that executes those jobs the accumulated rate by which storage is being filled. Also shown is the number of hours before the disk storage will be totally filled under those rates.

Release Notes on calculating wait time--

For transactions where user "wait" time is of interest, NetRule's MT module now has a client blocking parameter. This parameter allows you to define whether work continues or not during the response wait time. If work does not proceed until a response is received, this wait time contributes to utilization and the multi-tier transaction time.

For a simple example of this new feature in the MT module, open analyst.net.

This model has one multi-tier job with 2 tiers. A sensor (tier 1)sends information to 10 analysts who process the information and decide if they should respond to the information. They respond to the information by submitting a database entry 50% of the time (tier 2). The analysts cannot continue work until they receive a response from the server when they generate the database work.

1. On the "do DB" job profile, 100% has been entered for the client blocking parameter.
2. After evaluating, you will see that the analysts are waiting 9.2% of the time. Their average wait time is almost 2 seconds. You will find a summary of wait times in the report "Waiting for Reply" under the menu option RESULTS. The numbers are also shown on the job pages.

*** NOTICE ***

If you have models that are in the 4.1 or prior formats, please save them in the 4.2 format before installing Release 4.3. The new release will convert your 4.2 nets to 4.3, but it will not convert nets from releases prior to 4.2!