You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2015/03/12 20:19:38 UTC

[jira] [Updated] (SOLR-7239) StatsComponent perf improvement for min, max, and situations where all stats disabled

     [ https://issues.apache.org/jira/browse/SOLR-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man updated SOLR-7239:
---------------------------
    Attachment: SOLR-7324.patch

this patch optimizes away the "none" stat case, as well as caches the min/max numeric values in a double primitive (the Double object is still used for the null check in the event that no values exist at all)

> StatsComponent perf improvement for min, max, and situations where all stats disabled
> -------------------------------------------------------------------------------------
>
>                 Key: SOLR-7239
>                 URL: https://issues.apache.org/jira/browse/SOLR-7239
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>         Attachments: SOLR-7324.patch
>
>
> as mentioned in SOLR-6349, when i started doing perf testing of requesting individual stats, i noticed that min (and it turns out max) were slower to compute then more complex stats like sum & mean.
> While investigating, i realized that we can also optimize the case where a stats.field param is specified, but no stats are computed for example: stats.field={!min=$doMin}fieldname&doMin=false



--
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