[MGNLRES-177] Optimise ResourcesContainer by caching items Created: 30/Jun/15 Updated: 29/Mar/22 Resolved: 01/Jul/15 |
|
| Status: | Closed |
| Project: | Magnolia Resources Module |
| Component/s: | None |
| Affects Version/s: | 2.4 |
| Fix Version/s: | 2.4.1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Ilgun Ilgun |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | resources-app | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 3h | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: | |
| Sprint: | Sprint 3 (Basel) |
| Story Points: | 1 |
| Team: |
| Description |
|
Currently each time ResourceContainer#getItem() is called - a new Vaadin Item is created, which means every time ResourceContainer#getContainerProperty(...) is invoked - another item with n-properties is instantiated which leads to a significant memory footprint and potential issues with scalability. Simple hash-map based cache with a limited capacity would already help a lot. |
| Comments |
| Comment by Ilgun Ilgun [ 01/Jul/15 ] |
|
Changes can be found at branch feature/optimize-resourcecontainer |