[
https://issues.apache.org/jira/browse/ISIS-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687231#comment-16687231
]
Andi Huber commented on ISIS-2031:
----------------------------------
Symptoms go away with disabling L1 cache verification:
isis.persistor.datanucleus.impl.datanucleus.findObject.validateWhenCached=false
>From DN's webpage:
When you call the method getObjectById if an object with that identity is found
in the cache then a call is, by default, made to validate it still exists. You
can avoid this call to the datastore by setting the persistence property
datanucleus.findObject.validateWhenCached to false.
WE need to further investigate, whether we can optimize this on our side,
without disabling L1 cache verification.
> Using 'show all' on tables does take longer than expected
> ---------------------------------------------------------
>
> Key: ISIS-2031
> URL: https://issues.apache.org/jira/browse/ISIS-2031
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: Wicket
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Minor
> Fix For: 2.0.0-M2
>
>
> When fetching and displaying 25 objects (rendering a table) takes 1s, then
> the same with 100 objects should take about 4s, but it takes way longer.
> This is strange. I also noticed, that after having fetched all objects from
> the DB, the viewer is still occupied with rendering, showing the long-running
> indicator.
> This needs some investigation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
