Project:
| View Revisions: Issue #37336 | [ Back to Issue ] | ||
| Summary | 0037336: Performance of Warehouse Control Report | ||
| Revision | 2017-11-23 15:06 by rbianchini | ||
| Steps To Reproduce | 1 - Open the Warehouse Control Report, on an environment with more than a half million of records on the m_transaction. | ||
| Revision | 2017-11-23 15:06 by rbianchini | ||
| Description | When the m_transaction is too large, there is a performance problem with this report, when the window is opened, there is a delay of a few minutes, even sometimes, it locks the system, depending on the server load at that moment. We discovered that when the report is opened, it executes the query and it is not necessary. | ||
| Revision | 2017-11-23 14:49 by rbianchini | ||
| Steps To Reproduce | 1 - Open the Warehouse Control Report, on an environment with more than a half million of records on the m_transaction. 2 - Set something on the attribute filter. 3 - Run the report. |
||
| Revision | 2017-11-23 14:49 by rbianchini | ||
| Description | When the m_transaction is too big, there is a performance issue with this report, and even when the windows is opening, there is a delay of 2 or 3 minutes, depending of the server charge on that moment. Then when the the Attribute filter is not empty, the performance of the running report is worst. | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |