You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Shad Storhaug (Jira)" <ji...@apache.org> on 2020/01/25 02:40:00 UTC
[jira] [Resolved] (LUCENENET-634) Investigate using alternative
ConcurrrentHashSet implementation
[ https://issues.apache.org/jira/browse/LUCENENET-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shad Storhaug resolved LUCENENET-634.
-------------------------------------
Resolution: Resolved
The ConcurentHashSet was brought into Lucene.Net.Support and made internal. Adding a dependency was possible, but the project isn't strong named so there was a warning, but we were also able to use it in more places by implementing {{ISet<T>}} and adding a working {{UnionWith}} implementation.
> Investigate using alternative ConcurrrentHashSet implementation
> ---------------------------------------------------------------
>
> Key: LUCENENET-634
> URL: https://issues.apache.org/jira/browse/LUCENENET-634
> Project: Lucene.Net
> Issue Type: Task
> Components: Lucene.Net Core
> Affects Versions: Lucene.Net 4.8.0
> Reporter: Shad Storhaug
> Priority: Minor
> Labels: performance, up-for-grabs
>
> There is a lower level implementation of ConcurrentHashSet available on NuGet that supports all of our target platforms:
> https://github.com/i3arnon/ConcurrentHashSet/blob/master/src/ConcurrentHashSet/ConcurrentHashSet.cs
> The only limitation is that it does not actually implement {{ISet<T>}}. I don't believe that will be a problem, though. But, since this collection is used directly in {{IndexReader}} it is worth looking into.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)