Displaying 2 results from an estimated 2 matches for "last_doc_id".
2018 Apr 06
1
sorting large msets
...gt; > This is because in that case we can just stop once we've found 200
> > > matches.
With a few million documents, that ENQ_ASCENDING sounds promising :)
So, it looks like if I had ideal ordering, I could do something
along the lines of:
my $doc_id = $db->get_metadata('last_doc_id') || 0xffffffff;
$db->replace_document($doc_id--, $_) foreach (@doc);
$db->set_metadata('last_doc_id', $doc_id);
And get killer performance.
Olly Betts <olly at survex.com> wrote:
> On Sat, Mar 31, 2018 at 12:58:19AM +0000, Eric Wong wrote:
> > Would it be pos...
2018 Mar 31
2
sorting large msets
Olly Betts <olly at survex.com> wrote:
> On Fri, Mar 30, 2018 at 05:21:43PM +0000, Eric Wong wrote:
> > Hello, is there a way to optimize sorting by certain values
> > for queries which return a huge amount of results?
> [...]
> > $enquire->set_sort_by_value_then_relevance(0, 1);
>
> If you're just wanting the 200 newest, it'll be faster not to