quite frankly: IMHO the bigger impact on memory usage is
that afaik we currently load all parent states which most likely
will not be all accessed by the oak/jcr API calls. what we keep
having in CQ apart from the original installation rather
resembles random access (here a image node, from there the
design from the third location the script to render it and so
forth) than strict hierarchical access.
kind regards
angela
On 3/22/13 12:48 PM, Michael Dürig wrote:
On 19.3.13 15:09, Marcel Reutegger wrote:
how about caching the path in ImmutableTree? IIUC this tree
implementation works on top of NodeStates, which means the
path will never change, right?
Caching the path has a quite bad impact on memory usage. See
http://markmail.org/message/xhlr44umptmdnxck
Michael
