are
> taking more time comparatively?
>
> On Sun, 27 May 2018, 06:02 Will Currie, wrote:
>
> > I raised https://issues.apache.org/jira/browse/SOLR-12407. In case
> anybody
> > else sees a similar slowdown with boosts.
> >
> > On Sat, May 26, 2018 at 4:10 PM, Wil
I raised https://issues.apache.org/jira/browse/SOLR-12407. In case anybody
else sees a similar slowdown with boosts.
On Sat, May 26, 2018 at 4:10 PM, Will Currie wrote:
> I did some more (micro)benchmarking with a single query. Setting the query
> cache size to zero I see 400ms response t
archer.search(IndexSearcher.java:462)
at
org.apache.solr.search.SolrIndexSearcher.buildAndRunCollectorChain(SolrIndexSearcher.java:215)
What's the history behind Scorer returning floats but other code using
doubles?
Sorry if this is the wrong list to vommit out jstack dumps.
Thanks!
On Fri, May 25, 2018 at 3:23 PM, Will Curr
I'm seeing 0.5s increase in avg and p99 latencies after upgrading from 7.2
to 7.3.1. Eg 1s avg to 1.5s avg.
I've tried upgrading from java 8 to 10 (9 being EOL) suspecting
https://issues.apache.org/jira/browse/LUCENE-7966. No help.
I'm using boost queries. Probably abusing boost queries. Jstack l
Thanks. Done. https://issues.apache.org/jira/browse/SOLR-12321
On Mon, May 7, 2018 at 12:56 PM, Mark Miller wrote:
> Yeah, the project should never use built in serialization. I'd file a JIRA
> issue. We should remove this when we can.
>
> - Mark
>
> On Sun, May 6, 2018
Premise: During an upgrade I should be able to run a 7.3 pull replica
against a 7.2 tlog leader. Or vice versa.
Maybe I'm totally wrong in assuming that!
Assuming that's correct it looks like adding a new method[1] to
SolrResponse has broken binary compatibility. When I try to register a new
pull
