Before you deploy and monitor custom action, consider the following performance factors
- Business needs.
Determine how frequently the application status must be updated.
- PerlScript performance
Polling each object might take considerable time to complete. Before you decide to configure to monitor a custom action, consider the possible delays that might be introduced by PerlScript. For example, your requirement is to update the status every 4 minutes and the polling group contains more than 50 objects. Each PerlScript takes 5 seconds to complete one update. In this case, it takes at least 4 minutes and 10 seconds before attributes in the software service objects are updated. In order to meet the business requirement of 4 minute polling cycle, each PerlScript should handle smaller set of groups.
- Number of PerlScript processes
The maximum number of PerlScript instances at any given time is the number of threads configured in the Integration Accessor. The default value is 10.
