jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Angela Schreiber (Jira)" <j...@apache.org>
Subject [jira] [Updated] (OAK-8673) Determine and possibly adjust size of eagerCacheSize
Date Thu, 31 Oct 2019 14:49:00 GMT

     [ https://issues.apache.org/jira/browse/OAK-8673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Angela Schreiber updated OAK-8673:
----------------------------------
    Description: 
The initial results of the {{EagerCacheSizeTest}} seem to indicate that we almost never benefit
from the lazy permission evaluation (compared to reading all permission entries right away).
From my understanding of the results the only exception are those cases where only very few
items are being accessed (e.g. reading 100 items).

However, I am not totally sure if this is not a artifact of the random-read. I therefore started
extending the benchmark with an option to re-read a randomly picked item more that once, which
according to some analysis done quite some time ago is a common scenario specially when using
Oak in combination with Apache Sling.

Result are attached to OAK-8662 (possibly more to come).



  was:Based on the result of 


> Determine and possibly adjust size of eagerCacheSize
> ----------------------------------------------------
>
>                 Key: OAK-8673
>                 URL: https://issues.apache.org/jira/browse/OAK-8673
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: core, security
>            Reporter: Angela Schreiber
>            Assignee: Angela Schreiber
>            Priority: Major
>
> The initial results of the {{EagerCacheSizeTest}} seem to indicate that we almost never
benefit from the lazy permission evaluation (compared to reading all permission entries right
away). From my understanding of the results the only exception are those cases where only
very few items are being accessed (e.g. reading 100 items).
> However, I am not totally sure if this is not a artifact of the random-read. I therefore
started extending the benchmark with an option to re-read a randomly picked item more that
once, which according to some analysis done quite some time ago is a common scenario specially
when using Oak in combination with Apache Sling.
> Result are attached to OAK-8662 (possibly more to come).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message