Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0023490 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] A. Platform | major | have not tried | 2013-04-04 12:50 | 2013-04-04 12:51 | |||||||
| Reporter | alostale | View Status | public | |||||||||
| Assigned To | AugustoMauch | |||||||||||
| Priority | urgent | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Web browser | ||||||||||||
| Modules | Core | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0023490: Alert Management window doesn't scale | |||||||||||
| Description | Alert Management window has some design defects that cause it not to scale in case the amount of alerts is high. 1. When the window is opened, AlertManagementActionHandler is invoked. It is in charge of retrieving the list of alert rule that apply to current user/role (which in general shouldn't be big enough to cause problems). In case the Alert Rule has a Filter Clause, a list of *all* alert instances applicable to the user/role is retrieved, this is very prone to be problematic (see issue 0023482). 2. The information obtained from AlertManagementActionHandler is sent back to datasource for each of the four grids displayed in the window, so the query in backed in composed based on this info. 3. Datasource for "Solved" grid (which is closed by default) is requested on window opening. This grid keeps a history of all alerts, so it can be huge and it is rarely opened. | |||||||||||
| Steps To Reproduce | - | |||||||||||
| Proposed Solution | Below proposed solution for each of the items in the description. 1. AlertManagementActionHandler shouldn't retrieve the instances of all alerts, and ideally not even the alert rules. 2. Instead of using a standard datasource, a manual one could be used. This one would do all the stuff currently AlertManagementActionHandler is doing. So the only required parameter would be the grid type. 3. Do not request "solved" grid till it is opened in the UI. | |||||||||||
| Tags | Performance | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-04-04 12:50 | alostale | New Issue | |
| 2013-04-04 12:50 | alostale | Assigned To | => AugustoMauch |
| 2013-04-04 12:50 | alostale | Modules | => Core |
| 2013-04-04 12:50 | alostale | Triggers an Emergency Pack | => No |
| 2013-04-04 12:51 | alostale | Relationship added | related to 0023482 |
| 2013-04-04 12:51 | alostale | Tag Attached: Performance | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |