Page History
This section includes the following topic:
| Anchor | ||||
|---|---|---|---|---|
|
With the Load Data process parameters you are able to filter the Load Data results better, providing you with a better overview of the actual data. After selecting this parameter, you can select the instance for which you want to make changes to the default settings.
...
| Parameter | Default value |
|---|---|
| Too many queued ASP.NET requests | Maximum request queue length n queued items (5). |
| Long wait time for ASP.NET requests | Maximum request wait time n milliseconds (1000). |
| Incorrect ASP.NET API cache usage - low hit ratio | Minimum cache hit ratio n percent (80). |
| Incorrect ASP.NET API cache usage - high turnover rate | Maximum cache turnover ratio n turnovers/second (100). |
| Incorrect ASP.NET output cache usage - low hit ratio | Minimum cache hit ratio n percent (80). |
| Incorrect ASP.NET output cache usage - high turnover rate | Maximum cache turnover ratio n turnovers/second (100) |
| Too many ASP.NET errors | Maximum errors per request ratio (5). |
| Too many unhandled ASP.NET exceptions | Maximum number of unhandled exceptions (0). |
| Too much time in garbage collection | Normal CPU utilizations n percent (70). Maximum time in garbage collection for low CPU utilization n percent (5). Maximum time in garbage collection for high CPU utilization n percent (10). |
| Object allocation problem | |
...
| Maximum ratio garbage collection generations n percent (20). |
| Too many garbage collection calls by |
...
| user | Maximum number of induced garbage collection calls (0) |
...
| Too many exceptions |
...
| thrown | Maximum number of thrown exceptions per second (50). |
| Contention rate too |
...
| high | Maximum number of unsuccessful locks per second (50). |
| Incorrect connection string |
...
| usage | Maximum number of different connection strings to database (10). |
| Slow database open |
...
| connection | Maximum database open connection time n seconds (2). |
| Slow database requests |
...
| execution | Maximum database execution time n seconds (10). |
| Slow page |
...
| load | Maximum page load time n seconds (5). |
| Slow Web service |
...
| invocation | Maximum Web service invocation time n seconds (5). |
| Slow XML document |
...
| load | Maximum XML load time n seconds (2). |
| Incorrect garbage collection |
...
| usage | Maximum number of garbage collection calls (0). |
| Slow |
...
| serialization | Maximum serialization time per invocation time ratio n percent (10). |
| Slow de- |
...
| serialization | Maximum de-serialization time per invocation time ratio n percent (10). |
| Too many calls for |
...
| serialization | Maximum number of serialization invocations per second (100). |
| Too many calls for de- |
...
| serialization | Maximum number of de-serialization invocations per second (100). |
| Incorrect usage of the Finalize |
...
| method | Maximum number of calls to the finalized method (0). |
...
| Too many method |
...
| invocations | Maximum method time n seconds (0.3). Maximum number of method invocations (100). |
| Too much time in |
...
| lock | Maximum time in lock n seconds (0.2). |
...
About the Oracle Collect Bind Variables process parameter
The Oracle Collect Bind Variables process collects bind sets that were used while the statements were run (applicable for Oracle 10.1.0.4 and later). You can specify which mandatory statements to collect binds for by specifying their statement hash values, separated by a semicolon.
...