Page History
...
ContentApps + containers
tree
is not using paging - reads all child nodes when expanding
list
- queries for all elements to get total size - then queries the content using a paging mechanism
thumbnail
- doesn't extend AbstractJcrContainer - hence it cannot , doesn't use its paging mechanism
- has its own lazy loading mechanism: loads when required but then keeps all read items (images) until we switch to another view
...
- starting contacts app consumes 20-30 MByte of additional memory
- could not measure a diff between querying "select *..." of "select [jcr:uuid]..." in AbstractJcrContainer#updateSize()
- list view temporarily consumes about 100 MByte but this goes aways on GC - this is true even when scrolling around
- thumbnail view easily consumes about 200 MByte when scrolling in it - this memory stays after GC and is only freed when switching to another viewsystem gets pretty slow bug most memory is freed using GC
Overview
Content Tools