AnA03S02PerformanceOrderEdition
TWiki>
LibrePlan Web>AnA03S02PerformanceOrderEdition (08 Nov 2010, JavierMoran)EditAttach
| Story summary | Performance tuning in order edition window |
| Iteration | AnA03PerformanceTuning |
| FEA | AnA03S02PerformanceOrderEdition |
| Story Lead | |
| Next Story | |
| Passed acceptance test | No |
The validation of being unique the order code has to be changed from being validated in the entities to be validated in the XXXModel becuase the validation is runned for each order element. It is needed just to execute it once for all the order elements of an order.
The same has to be done for the codes of the hours group. It has to be moved the validation from entities to XXXModel.
It is important to realize that it will be needed to change the import system in order to do these validations too.
When an order is saved it is reloaded completely. This causes an unnecessary delay because in this case this could be avoided.
This can be avoided. The only field that changes is the code. So we have three options to assess:
- Really not load the generated code and in this case, not update the order completely.
- Assess if update quickly only this column without reloading is an option.
- Generate the code in the moment of adding the line to the order.
Of course, we have to see if technically the objects in the model have the ids and the codes generated although we do not reload the tree.
Now it is being used a paginated tree for editing an order with a page size of 50 elements per size. With this size, the change of page is really slow. So, we need to improve the times to browse and use the tree.
Steps to do are (not needed in this order):
- Measure the time is being consumed in the interface for the rendering of these trees with this number of elements.
- Do tests to identify inside a row the elements which takes longer to render. Assess if we can change some of the widgets of a row and delete and simplify these rows.
- Assess solutions as load-on-demand. Can it be applied?
- Checkout the ZK5 branch and make a merge to have it updated with the last changes in the repo. Assess if with the ZK5 version of the framework we have a better performance.
- As a last solution we could reduce the size of the page - to 20 elements -. It would be nice to be able to show some feedback while changing the page it is being visited.
Copyright (c) by the contributing authors. All material on this collaboration platform is the property of the contributing authors.