Implementing additional iConsole servers to distribute the workload will alleviate this situation, alternatively you can apply some registry settings to optimize search efficiency and avoid cache timeouts.
The following settings are aimed at making the WebService more scalable and avoid frequent recycling of application pools. These settings can be adjusted to reduce the cache usage. The recommended values are pointers and should be adjusted according to the usage and environment.
1. Only return events you need. Set the "Basic Filters" in the iConsole search to control the scope of the search. For example, date range and number of events being fetched by the search.
2. “MaximumResultSetSize” is set by default at 1000. Do not change this value, higher values return more results but also consume more memory.
3. "SearchResultsCachePeriodMinutes" - Decreasing this value will help re-claim unused data sooner than later. Consider setting to 20 minutes or less.
4. "EventCachePeriodMinutes" - When an event is viewed, all the details of the event along with its blob are retrieved and stored in cache. This is to enable faster viewing of the same event in future, but this does use up resources. This setting should be adjusted based on the reviewer's behavior. If an already viewed event does not need revisiting, it is recommended to decrease the value. For example reducing the time to 1 minute.
Note: To implement changes, reset the IIS service after making changes to the registry .