You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2019/09/13 18:38:46 UTC

[GitHub] [lucene-solr] mikemccand commented on issue #877: LUCENE-8978: Maximal Bottom Score Based Early Termination

mikemccand commented on issue #877: LUCENE-8978: Maximal Bottom Score Based Early Termination
URL: https://github.com/apache/lucene-solr/pull/877#issuecomment-531346943
 
 
   > I ran luceneutil with concurrent mode and wikimedium2m -- no degradation to QPS and some tasks show a reduction of around 30% in latencies.
   
   We have to be careful interpreting luceneutil results: it does not run a true "red-line" (capacity) test.  When it reports QPS, that's the result of N threads running random queries over and over, not necessarily saturating CPU/IO on the server you are testing on.
   
   In fact, it's odd you didn't see a QPS gain when you saw latency improvements -- those latency gains should have meant the search threads run more queries per second, hmm.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org