You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2016/04/21 15:12:25 UTC
[jira] [Updated] (LUCENE-7237) LRUQueryCache should rather not
cache than wait on a lock
[ https://issues.apache.org/jira/browse/LUCENE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand updated LUCENE-7237:
---------------------------------
Summary: LRUQueryCache should rather not cache than wait on a lock (was: LRUQueryCache )
> LRUQueryCache should rather not cache than wait on a lock
> ---------------------------------------------------------
>
> Key: LUCENE-7237
> URL: https://issues.apache.org/jira/browse/LUCENE-7237
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
>
> This is an idea Robert just mentioned to me: currently the cache is using a lock to keep various data-structures in sync. It is a pity that you might have contention because of caching. So something we could do would be to not cache when the lock is already taken.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org