jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2619) improved internal representation of DATE values
Date Mon, 26 Apr 2010 22:57:31 GMT

    [ https://issues.apache.org/jira/browse/JCR-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861155#action_12861155
] 

Jukka Zitting commented on JCR-2619:
------------------------------------

The tradeoff between a string and a binary representation is the performance impact on having
to generate the string when the getString() method is called. If that's not a concern, then
I'd actually suggest that we simply use a single long value and avoid all object or array
overhead.

> improved internal representation of DATE values
> -----------------------------------------------
>
>                 Key: JCR-2619
>                 URL: https://issues.apache.org/jira/browse/JCR-2619
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, jackrabbit-spi-commons
>            Reporter: Stefan Guggisberg
>             Fix For: 2.2.0
>
>         Attachments: JCR-2619_improved_internal_representation_of_DATE_values.patch
>
>
> DATE values are currently internally represented as java.util.Calendar objects.
> Calendar objects have a huge memory footprint (approx 200bytes per instance) 
> and are mutable.
> i suggest to replace the internal DATE representation with a ISO8601 format string
> (immutable and approx. 85-90% smaller footprint).

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


Mime
View raw message