lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (LUCENE-8213) Cache costly subqueries asynchronously
Date Tue, 26 Nov 2019 06:33:01 GMT


ASF subversion and git services commented on LUCENE-8213:

Commit 2d98a619dd96abfa716098bbc5cac2bc3a1b7d49 in lucene-solr's branch refs/heads/master
from Atri Sharma
[;h=2d98a61 ]

LUCENE-8213: Asynchronous Caching in LRUQueryCache (#916)

* LUCENE-8213: Introduce Asynchronous Caching in LRUQueryCache

> Cache costly subqueries asynchronously
> --------------------------------------
>                 Key: LUCENE-8213
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/query/scoring
>    Affects Versions: 7.2.1
>            Reporter: Amir Hadadi
>            Priority: Minor
>              Labels: performance
>         Attachments: 0001-Reproduce-across-segment-caching-of-same-query.patch, thetaphi_Lucene-Solr-master-Linux_24839.log.txt
>          Time Spent: 21h 10m
>  Remaining Estimate: 0h
> IndexOrDocValuesQuery allows to combine costly range queries with a selective lead
iterator in an optimized way. However, the range query at some point gets cached by a querying
thread in LRUQueryCache, which negates the optimization of IndexOrDocValuesQuery for that
specific query.
> It would be nice to see an asynchronous caching implementation in such cases, so that
queries involving IndexOrDocValuesQuery would have consistent performance characteristics.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message