[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036128#comment-16036128
]
Ishan Chattopadhyaya edited comment on SOLR-10317 at 6/4/17 12:30 AM:
----------------------------------------------------------------------
I'm very confused. Are you planning to use Shalin's benchmarking utility and
extend upon it? If no, why not?
Please understand that Shalin or I are NOT asking you to use one
platform/utility or the other, but simply asking you for a clarification on the
motivations behind *why* you are building a new platform you are using instead
of something that already exists. So far, I just see no clear answer, just
beating around the bush.
In terms of the differences, two good things I like about the reports that
Shalin's suite generates
(https://issues.apache.org/jira/secure/attachment/12843260/indexing.html) are:
# all graphs can be viewed at once
# supports tagging/addition of significant events
If you choose not to use Shalin's suite, can you please address these two
issues in the new suite that you are building?
was (Author: ichattopadhyaya):
I'm very confused. Are you planning to use Shalin's benchmarking utility and
extend upon it? If no, why not?
Please understand that Shalin or I are NOT asking you to use one
platform/utility or the other, but simply asking you for a clarification on the
motivations behind *why* you are building a new platform you are using instead
of something that already exists. So far, I just see no clear answer, just
beating around the bush.
In terms of the differences, two good things I like about the reports that
Shalin's suite generates
(https://issues.apache.org/jira/secure/attachment/12843260/indexing.html) are:
# all graphs can be viewed at once
# supports tagging/addition of significant events
If you choose not to use Shalin's suite, can you please address these two
issues in the new suite that you are building?
> 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,
> 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 [[email protected]] would help here.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
