[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106352#comment-16106352
]
Vivek Narang edited comment on SOLR-10317 at 7/30/17 7:45 AM:
--------------------------------------------------------------
Hi [~ichattopadhyaya]
bq. Your README file [0] is unreadable due to horizontal scrollers in each
section.
Fixed now please check.
[https://github.com/viveknarang/lucene-solr/tree/SolrNightlyBenchmarks/dev-tools/SolrNightBenchmarks]
bq. You need to be specific in terms of steps the user needs to take.
https://github.com/viveknarang/lucene-solr/tree/SolrNightlyBenchmarks/dev-tools/SolrNightBenchmarks#steps-to-launch
The steps have always existed on this file! Do you find any steps missing?
bq. Why are you calling it "test data files"?
Please suggest what you want these files to be referred as.
bq. Also, as a user, I don't fucking care about what ability the system has.
The referred part has been removed from the README file.
bq. Couldn't you spare 5 minutes from those 8-16 hours (in last 2 days) to get
to this?
I wanted to finish a group of important in-progress tasks before updating the
TODO items.
bq. Going forward, can you kindly post the daily status here in JIRA and
include sufficient details on work you have done each day?
Sure!
bq. Secondly, "please use the link provided below" is equivalent to telling the
user to "go f*** yourself"
The link has been provided as an option and is not a required step. When the
user has configured the system to automatically download required files, there
is no need for the user to manually download files.
bq. This is just unnecessary complexity to the system. Add a shell script to
download the data files (similar to the one I pasted above) [0].
I don't think there is any complexity here. Checking the existence of these
files is already an essential step. The files are only downloaded when missing
and essentially a wget is done to download files please see code below. If you
still insist I will create a shell script for this.
[https://github.com/viveknarang/lucene-solr/blob/SolrNightlyBenchmarks/dev-tools/SolrNightBenchmarks/src/main/java/org/apache/solr/tests/nightlybenchmarks/Util.java#L737]
was (Author: vivek.nar...@uga.edu):
Hi [~ichattopadhyaya]
bq. Your README file [0] is unreadable due to horizontal scrollers in each
section.
Fixed now please check.
[https://github.com/viveknarang/lucene-solr/tree/SolrNightlyBenchmarks/dev-tools/SolrNightBenchmarks]
bq. You need to be specific in terms of steps the user needs to take.
https://github.com/viveknarang/lucene-solr/tree/SolrNightlyBenchmarks/dev-tools/SolrNightBenchmarks#steps-to-launch
The steps have always existed on this file! Do you find any steps missing?
bq. Why are you calling it "test data files"?
Please suggest what you want these files to be referred as.
bq. Also, as a user, I don't fucking care about what ability the system has.
The referred part has been removed from the README file.
bq. Couldn't you spare 5 minutes from those 8-16 hours (in last 2 days) to get
to this?
I wanted to finish a group of important in-progress tasks before updating the
TODO items.
bq. Going forward, can you kindly post the daily status here in JIRA and
include sufficient details on work you have done each day?
Sure!
> 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
