[
https://issues.apache.org/jira/browse/SOLR-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193227#comment-15193227
]
Steve Shabino commented on SOLR-3475:
-------------------------------------
I believe the synchronization exists so that multiple, concurrent requests for
the same cache key do not cause redundant construction of the (likely
expensive) cached value. This ought to be a feature of the cache, as done by
Guava or Caffeine via their LoadingCache interfaces.
> Performance hit due to unnecessary syncronization
> -------------------------------------------------
>
> Key: SOLR-3475
> URL: https://issues.apache.org/jira/browse/SOLR-3475
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.1
> Reporter: Varun Srivastava
>
> Method org.apache.solr.request.UnInvertedField.getUnInvertedField unnecessary
> syncronize agiant cache object. The SolrCache implementations should them
> selves be thread safe. For example FastLRUCache uses ConcurrentLRUCache which
> in turn use java.util.concurrency structs to make the implementation
> threadsafe.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
