Status Quo

Running performance tests against M5 (beta2) we got the impression that M5 is consuming quite a lot of memory per user. That's why we wanted to optimize.

Analysed Components 

ContentApps + containers

tree

list

thumbnail

• doesn't extend AbstractJcrContainer - hence it cannot use its paging mechanism
• is lazy - but keeps all the read items (images) until we switch to another view

Setup

For the analysis we used the contacts app. There we added 10'000 contacts all having a random street (2000 chars), city (100 chars) + organization name (20'000 chars) as well as one identical image (11kbyte).