[jira] [Updated] (OAK-3259) Optimize NodeDocument.getNewestRevision()

2015-08-25 Thread Marcel Reutegger (JIRA) 

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

Marcel Reutegger updated OAK-3259:
--
Fix Version/s: 1.2.5
   1.0.20

Merged into 1.2 branch: http://svn.apache.org/r1697567

and 1.0 branch: http://svn.apache.org/r1697580

 Optimize NodeDocument.getNewestRevision()
 -

 Key: OAK-3259
 URL: https://issues.apache.org/jira/browse/OAK-3259
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: core, mongomk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
  Labels: performance
 Fix For: 1.3.5, 1.0.20, 1.2.5


 Most of the time NodeDocument.getNewestRevision() is able to quickly identify 
 the newest revision, but sometimes the code falls to a more expensive 
 calculation, which attempts to read through available {{_revisions}} and 
 {{_commitRoot}} entries. If either of those maps are empty, the method will 
 go through the entire revision history.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OAK-3259) Optimize NodeDocument.getNewestRevision()

2015-08-24 Thread Marcel Reutegger (JIRA) 

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

Marcel Reutegger updated OAK-3259:
--
Labels: performance  (was: resilience)

 Optimize NodeDocument.getNewestRevision()
 -

 Key: OAK-3259
 URL: https://issues.apache.org/jira/browse/OAK-3259
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: core, mongomk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
  Labels: performance
 Fix For: 1.3.5


 Most of the time NodeDocument.getNewestRevision() is able to quickly identify 
 the newest revision, but sometimes the code falls to a more expensive 
 calculation, which attempts to read through available {{_revisions}} and 
 {{_commitRoot}} entries. If either of those maps are empty, the method will 
 go through the entire revision history.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OAK-3259) Optimize NodeDocument.getNewestRevision()

2015-08-24 Thread Michael Marth (JIRA) 

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

Michael Marth updated OAK-3259:
---
Labels: resilience  (was: )

 Optimize NodeDocument.getNewestRevision()
 -

 Key: OAK-3259
 URL: https://issues.apache.org/jira/browse/OAK-3259
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: core, mongomk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger
  Labels: resilience
 Fix For: 1.3.5


 Most of the time NodeDocument.getNewestRevision() is able to quickly identify 
 the newest revision, but sometimes the code falls to a more expensive 
 calculation, which attempts to read through available {{_revisions}} and 
 {{_commitRoot}} entries. If either of those maps are empty, the method will 
 go through the entire revision history.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)