[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018774#comment-16018774
]
Ishan Chattopadhyaya commented on SOLR-10317:
---------------------------------------------
bq. What could be the cause of variation in performance?
I have no insight into what you're referring to. I don't even know what the
test does and how.
bq. Please let me know soon!
I'm currently recovering from a bad food poisoning, and unable to work :-( Can
you please provide steps to reproduce, and describe what exactly you're doing
and what exactly are you concerned about? Also, do you think your sample size
of data points is sufficient to determine that the variation you're observing
is an actual outlier, and not just statistical noise? You could discuss any
usage related issues (like indexing performance, collection creation etc.) in
the solr-users mailing list, and you would get more insightful answers. If you
establish the degradation as a significant one, and/or as a result of a bug,
feel free to file a JIRA for it.
GSoC is about "open source" contributions, and this is your "community bonding"
period. I neither see that you've provided any links to your source code, nor
do I see your participation in any community bonding activities. I don't even
know much about the underlying design of the tool that you're building. (Maybe
you could start by contributing a patch here?) From an observer's point of
view, all I see from you are just some updates about the development of a
proprietary (non-free / non-open source) tool. This is contrary to the spirit
of the GSoC program, and I would like to encourage you to undertake some course
correction so as to make your participation in this program a success going
forward.
> 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 [~markrmil...@gmail.com] would help here.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
