You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2013/06/08 06:11:23 UTC

[jira] [Resolved] (SIS-85) Consider removing metadata synchronization

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

Chris A. Mattmann resolved SIS-85.
----------------------------------

    Resolution: Fixed
    
> Consider removing metadata synchronization
> ------------------------------------------
>
>                 Key: SIS-85
>                 URL: https://issues.apache.org/jira/browse/SIS-85
>             Project: Spatial Information Systems
>          Issue Type: Improvement
>          Components: Metadata
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>             Fix For: 0.3
>
>
> All subclasses of {{ISOMetadata}} are currently synchronized. It probably doesn't have significant impact on the JAR file size, since (in my understanding) adding a {{synchronized}} keyword in the method signature just set a bit in a bitmask. However it may be a cause of thread contention.
> Synchronization may not be necessary since the typical usage of metadata objects is:
> * Create the metadata object once in a single thread.
> * Declare the metadata as unmodifiable.
> * Allow any thread to read (but not set) the metadata properties.
> The potential contention, especially on metadata object shared by many other objects, would be unfortunate. However profiling this not show significant bottleneck yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira