[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106499#comment-16106499
]
Ishan Chattopadhyaya edited comment on SOLR-10317 at 7/30/17 1:51 PM:
----------------------------------------------------------------------
How can I see logs for these runs? Are they stored somewhere (as they should
be)?
Also, in the console logs, I see lines like these:
{code}
Ending State: | 0| 0| 238842| 0| 0| 0| 0| 0| 0| 0| 0
Ending State: | 0| 0| 238842| 0| 0| 0| 0| 0| 0| 0| 0
{code}
What do they mean?
Also, what do the following mean?
{code}
org.apache.solr.tests.nightlybenchmarks.QueryClient@427b6220** Getting out of
critical section ...
org.apache.solr.tests.nightlybenchmarks.QueryClient@25174eb0** Getting out of
critical section ...
org.apache.solr.tests.nightlybenchmarks.QueryClient@35ef7d35** Getting out of
critical section ...
{code}
Also, I saw the following exceptions:
{code}
java.lang.NullPointerException
at
org.apache.solr.tests.nightlybenchmarks.QueryClient.run(QueryClient.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
However, the execution continued without complaining. That shows that exception
handling is not proper. Such exceptions should be fatal and the entire
benchmarking suite should crash out after such exceptions. Silently ignoring
them seems like a horrible thing to do.
was (Author: ichattopadhyaya):
How can I see logs for these runs? Are they stored somewhere (as they should
be)?
Also, in the console logs, I see lines like these:
{code}
Ending State: | 0| 0| 238842| 0| 0| 0| 0| 0| 0| 0| 0
Ending State: | 0| 0| 238842| 0| 0| 0| 0| 0| 0| 0| 0
{code}
What do they mean?
Also, what do the following mean?
{quote}
org.apache.solr.tests.nightlybenchmarks.QueryClient@427b6220** Getting out of
critical section ...
org.apache.solr.tests.nightlybenchmarks.QueryClient@25174eb0** Getting out of
critical section ...
org.apache.solr.tests.nightlybenchmarks.QueryClient@35ef7d35** Getting out of
critical section ...
{quote}
Also, I saw the following exceptions:
{code}
java.lang.NullPointerException
at
org.apache.solr.tests.nightlybenchmarks.QueryClient.run(QueryClient.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
However, the execution continued without complaining. That shows that exception
handling is not proper. Such exceptions should be fatal and the entire
benchmarking suite should crash out after such exceptions. Silently ignoring
them seems like a horrible thing to do.
> Solr Nightly Benchmarks
> -----------------------
>
> Key: SOLR-10317
> URL: https://issues.apache.org/jira/browse/SOLR-10317
> Project: Solr
> Issue Type: Task
> Reporter: Ishan Chattopadhyaya
> Labels: gsoc2017, mentor
> Attachments: changes-lucene-20160907.json,
> changes-solr-20160907.json, managed-schema,
> Narang-Vivek-SOLR-10317-Solr-Nightly-Benchmarks.docx,
> Narang-Vivek-SOLR-10317-Solr-Nightly-Benchmarks-FINAL-PROPOSAL.pdf,
> SOLR-10317.patch, SOLR-10317.patch, solrconfig.xml
>
>
> Solr needs nightly benchmarks reporting. Similar Lucene benchmarks can be
> found here, https://home.apache.org/~mikemccand/lucenebench/.
> Preferably, we need:
> # A suite of benchmarks that build Solr from a commit point, start Solr
> nodes, both in SolrCloud and standalone mode, and record timing information
> of various operations like indexing, querying, faceting, grouping,
> replication etc.
> # It should be possible to run them either as an independent suite or as a
> Jenkins job, and we should be able to report timings as graphs (Jenkins has
> some charting plugins).
> # The code should eventually be integrated in the Solr codebase, so that it
> never goes out of date.
> There is some prior work / discussion:
> # https://github.com/shalinmangar/solr-perf-tools (Shalin)
> # https://github.com/chatman/solr-upgrade-tests/blob/master/BENCHMARKS.md
> (Ishan/Vivek)
> # SOLR-2646 & SOLR-9863 (Mark Miller)
> # https://home.apache.org/~mikemccand/lucenebench/ (Mike McCandless)
> # https://github.com/lucidworks/solr-scale-tk (Tim Potter)
> There is support for building, starting, indexing/querying and stopping Solr
> in some of these frameworks above. However, the benchmarks run are very
> limited. Any of these can be a starting point, or a new framework can as well
> be used. The motivation is to be able to cover every functionality of Solr
> with a corresponding benchmark that is run every night.
> Proposing this as a GSoC 2017 project. I'm willing to mentor, and I'm sure
> [~shalinmangar] and [~markrmil...@gmail.com] would help here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
