Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006272 | Openbravo ERP | I. Performance | public | 2008-11-30 18:18 | 2009-08-18 14:24 |
|
| Reporter | pjuvara | |
| Assigned To | iperdomo | |
| Priority | low | Severity | trivial | Reproducibility | always |
| Status | closed | Resolution | duplicate | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.40 | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0006272: Delete client slow processing |
| Description | Delete client is very slow. |
| Steps To Reproduce | |
| Proposed Solution | |
| Additional Information | |
| Tags | performance2.40scrum |
| Relationships | | duplicate of | defect | 0008575 | | closed | marvintm | Delete client operation takes about 1,5h | | depends on | backport | 0006972 | | closed | iperdomo | Delete client slow processing |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2008-11-30 18:18 | pjuvara | New Issue | |
| 2008-11-30 18:18 | pjuvara | Assigned To | => rafaroda |
| 2008-11-30 18:18 | pjuvara | sf_bug_id | 0 => 2365561 |
| 2008-11-30 18:18 | pjuvara | Regression testing | => No |
| 2008-11-30 18:19 | pjuvara | Tag Attached: performance2.40scrum | |
| 2008-11-30 18:19 | pjuvara | Assigned To | rafaroda => iperdomo |
| 2009-01-09 16:36 | psarobe | Note Added: 0012045 | |
| 2009-01-09 16:36 | psarobe | Status | new => feedback |
| 2009-01-10 19:37 | pjuvara | Note Added: 0012096 | |
| 2009-01-10 19:37 | pjuvara | Status | feedback => new |
| 2009-01-10 19:38 | pjuvara | Priority | normal => low |
| 2009-01-19 10:14 | psarobe | version | => 2.40 |
| 2009-01-19 10:14 | psarobe | Status | new => scheduled |
| 2009-01-19 10:14 | psarobe | fix_in_branch | => trunk |
| 2009-02-01 11:52 | iciordia | Note Added: 0012967 | |
| 2009-02-01 11:52 | iciordia | Type | defect => feature request |
| 2009-02-01 11:52 | iciordia | fix_in_branch | trunk => |
| 2009-08-18 14:23 | iperdomo | Relationship added | duplicate of 0008575 |
| 2009-08-18 14:24 | iperdomo | Status | scheduled => closed |
| 2009-08-18 14:24 | iperdomo | Duplicate ID | 0 => 8575 |
| 2009-08-18 14:24 | iperdomo | Resolution | open => duplicate |
|
Notes |
|
|
|
We intend to do everything possible to address this issue but, in order to resolve it successfully, we need additional information (environment, version).
Please provide the precise steps to reproduce it |
|
|
|
|
This is an issue I logged based on Stefan and Ivan's feedback.
During the performance testing (which is based on 2.40), they found that when they create a lot of data in a client, it takes too long to delete it and, in order to repeat a test, instead of simply deleting the client and restarting, they had to refresh the whole database.
I suggest that Ivan performs a simple test in the volume environment by deleting the client there. If it takes a reasonable amount of time (less than 2 hours), we can close this defect.
Otherwise it should be addressed based on its priority. |
|
|
|
|
To improve performance in delete client process is required to refactor the way it is implemented, using DAL capabilities.
Ismael |
|