You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2009/11/26 16:00:42 UTC

[jira] Reopened: (JCR-2327) java.util.UUID.fromString() too slow

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

Thomas Mueller reopened JCR-2327:
---------------------------------

      Assignee: Thomas Mueller

Creating a NodeId from a String is still a bottleneck. It's relatively easy to improve performance (avoiding creating temporary objects, use switch/case). There are some other issues: some errors are not detected, and the exception should include context information.

> java.util.UUID.fromString() too slow
> ------------------------------------
>
>                 Key: JCR-2327
>                 URL: https://issues.apache.org/jira/browse/JCR-2327
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Assignee: Thomas Mueller
>             Fix For: 2.0-beta4
>
>
> Benchmarking shows that the java.util.UUID.fromString() method is 10 times slower than the previous version we used from jackrabbit-jcr-commons. This method is quite heavily used in the query section or more generally whenever a NodeId is created from a String.
> I'd like to introduce the custom String UUID parsing code again that we had in the jackrabbit-jcr-commons UUID class and use it in the NodeId(String) constructor.
> WDYT?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.