You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2013/08/10 03:02:40 UTC
[jira] [Resolved] (LUCENE-5122) DiskDV probably shouldnt use
BlockPackedReader for SortedDV doc-to-ord
[ https://issues.apache.org/jira/browse/LUCENE-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved LUCENE-5122.
---------------------------------
Resolution: Won't Fix
I couldnt get any improvement out of this patch in benchmarks.
If someone does, let me know and we can reopen.
> DiskDV probably shouldnt use BlockPackedReader for SortedDV doc-to-ord
> ----------------------------------------------------------------------
>
> Key: LUCENE-5122
> URL: https://issues.apache.org/jira/browse/LUCENE-5122
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Attachments: LUCENE-5122.patch
>
>
> I dont think "blocking" provides any benefit here in general. we can assume the ordinals are essentially random and since SortedDV is single-valued, its probably better to just use the simpler packedints directly?
> I guess the only case where it would help is if you sorted your segments by that DV field. But that seems kinda wierd/esoteric to sort your index by a deref'ed string value, e.g. I don't think its even supported by SortingMP.
> For the SortedSet "ord stream", this can exceed 2B values so for now I think it should stay as blockpackedreader. but it could use a large blocksize...
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org