Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0011055 | Openbravo ERP | Y. DBSourceManager | public | 2009-10-20 17:32 | 2009-11-19 00:00 |
|
| Reporter | shuehner | |
| Assigned To | shuehner | |
| Priority | high | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | pi | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | No |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0011055: export.database and update.database could be 1min faster always |
| Description | The two steps:
Reading tables
Reading functions
each take about 30s use non optimized sql statements which could be easily made faster (around 1-2seconds each perhaps)
|
| Steps To Reproduce | |
| Proposed Solution | Example: reading functins
Change the upper(proname) = upper(?) to a simple proname = ? from the qeuries reading the function derails
and also remove the upper(proname) from the query reading the list of functions (to match the case).
Add an toUppercase when storing the procedure name into the Function object to not change behavior of other java dbsm code.
Apply the same idea to reading tables |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-10-20 17:32 | shuehner | New Issue | |
| 2009-10-20 17:32 | shuehner | Assigned To | => marvintm |
| 2009-10-20 17:32 | shuehner | OBNetwork customer | => No |
| 2009-10-20 17:32 | shuehner | Note Added: 0021223 | |
| 2009-10-20 17:32 | shuehner | Issue Monitored: shuehner | |
| 2009-11-11 18:45 | shuehner | Note Added: 0021735 | |
| 2009-11-11 18:46 | shuehner | Assigned To | marvintm => shuehner |
| 2009-11-11 19:23 | hgbot | Checkin | |
| 2009-11-11 19:23 | hgbot | Note Added: 0021736 | |
| 2009-11-11 19:23 | hgbot | Status | new => resolved |
| 2009-11-11 19:23 | hgbot | Resolution | open => fixed |
| 2009-11-11 19:23 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/9be52538e37fed0a8ee84d831f769c94fa0ccf32 [^] |
| 2009-11-18 11:12 | marvintm | Note Added: 0021955 | |
| 2009-11-18 11:12 | marvintm | Status | resolved => closed |
| 2009-11-19 00:00 | anonymous | sf_bug_id | 0 => 2900149 |
|
Notes |
|
|
|
|
Note: Speedup tested on postgres only, check if a similar change is useful in the oracle specified sql's |
|
|
|
|
The Read tables part of the theoretical speedup cannot be done easily.
The the "Reading functions..." takes about 0.5s on oracle and about 30s on postgres. The 30s on postgres can be speed up to 0.5 |
|
|
|
(0021736)
|
|
hgbot
|
|
2009-11-11 19:23
|
|
|
|
|
|
|
The changes are correct, and the export.database is definitely much faster. |
|