Problem Note 41394: Refreshing the Emerging Issue workspace can be slow after the status of an alert was updated
Refreshing the Emerging Issue workspace can be slow after you update the status of an alert or add a node. This problem occurs because the query for alerts is being run twice—first for the entire list and next for the current search selection option.
The default page size for the alert table for Enterprise and Ad-hoc Analytic is 20 alerts. You can configure this size using the eiAnalyticAlertTablePageSize property on the Advanced tab of the Warranty Analysis Properties dialog box in the SAS® Management Console Configuration Manager. When you want to change the setting for this property, you can expect one second of wait time for each alert that is on a page.
The size of the alert table for Ad-hoc Threshold is controlled by the lookupTablePageSize property, which has a default of 300 rows. (Note that you can also configure this property via the SAS Management Console Configuration Manager.) However, the SAS® Warranty Analysis 4.3 user interface displays only the graph that corresponds to the selected threshold analysis in the table. Releases prior to 4.3 (without hot fixes) used the lookupTablePageSize property to control the table page size, but displayed all of the graphs that corresponded to the threshold analyses on the displayed table page.
For Ad-hoc Threshold, only one graph is shown at a time. However, you can compare graphs using the Detach Chart… feature.
For better performance, use the search selection option to limit the number of alerts that display.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Warranty Analysis | Microsoft Windows 2000 Advanced Server | 4.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 4.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Server | 4.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Enterprise Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Standard Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
64-bit Enabled AIX | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
64-bit Enabled Solaris | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
HP-UX IPF | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
The problem occurs because the query for alerts is being run twice.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2011-01-14 11:07:54 |
Date Created: | 2010-10-26 07:53:09 |