You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Timothy Potter (JIRA)" <ji...@apache.org> on 2016/04/18 22:30:25 UTC
[jira] [Created] (SOLR-9008) Investigate feasibilty and impact of
using SparseFixedBitSet where Solr is currently using FixedBitSet
Timothy Potter created SOLR-9008:
------------------------------------
Summary: Investigate feasibilty and impact of using SparseFixedBitSet where Solr is currently using FixedBitSet
Key: SOLR-9008
URL: https://issues.apache.org/jira/browse/SOLR-9008
Project: Solr
Issue Type: Improvement
Reporter: Timothy Potter
Assignee: Timothy Potter
Found this gem in one of Mike's blog posts:
{quote}
But with 5.0.0, Lucene now supports random-writable and advance-able sparse bitsets (RoaringDocIdSet and SparseFixedBitSet), so the heap required is in proportion to how many bits are set, not how many total documents exist in the index.
{quote}
http://blog.mikemccandless.com/2014/11/apache-lucene-500-is-coming.html
I don't see any uses of either of these classes in Solr code but from a quick look, sounds compelling for saving memory, such as when caching fq's
This ticket is for exploring where Solr can leverage these structures and whether there's an improvement in performance and/or memory usage.
--
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