Optimization
From UG
Contents |
Info
Requirements
Keep system speed/performance at the normal levels NOW and IN THE FUTURE.
It is assumed that to satisfy above we have to:
- Optimize existing code, DB, etc to
- Develop strategy for the future development
SOW 0
- 0001357: (Misc) Create CT2 2015 DB (Ops/Acc modules) Test speed, optimize (requirements for how fast each CT2 table will grow attached)
For every table: a) record how many records are now b) find out (interview BAs) - how many records will be there at the end of 2010 c) estimate rate of growth per year after 2010 d) post this info into http://ct.jaguarfreight.com/wiki/Intro_into_CT2_DB [^] [^] Based on the info above CT2 Architect will: a) create database similar in size to dec 2010 levels b) estimate speed of application c) compare above with target d) optimize DB and algorithms to reach the target speed
SOW 1
* 0002233: (CT2 Misc) Ongoing DB optimization (SOW 1)
Implementation Notes SOW 1
- P/l for mult cts report refactoring
- Billing required report refactoring
- P/l report for CT group and for Master - lines from one PI for different cts was grouped into one line per Marc's request
SOW 2
- 0003312: (CT2 Misc) Ongoing DB optimization (SOW 2)
Implementation Notes SOW 2
1. Refactored ChargeCodes to ShipmentInvoices relation table (direct access without using tblTableOfCharges table). 2. Reworked ChargeCode persistence methods to speed-up Invoices access. Was improved speed of reports generation report p&l for multiple cts "Special View: Charge Code Group" optimized. this report now works 10-20 times faster
