[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020600#comment-16020600
]
Vivek Narang commented on SOLR-10317:
-------------------------------------
Hi [~ichattopadhyaya] I hope that you are well now.
I think I was right when I assumed that there was a memory issue when I was
testing on my previous server (with unsuitable hardware configuration for this
purpose). Thanks to migrating to the new server that you provided for this
project (8 Core 32 GB RAM), The indexing throughput is almost constant now,
even across recent consecutive commits. Please see
[http://212.47.227.9/dev/IndexingBenchmarkStandalone.html]. As you can observe
now in comparison with the setup on the previous server, the performance on
this server is consistent (with the difference of one second possibly due to
rounding off, which may also be statistically insignificant depending on how
precise we want to measure indexing performance). There is an exception noted
though, the indexing on a cluster of 5 Solr nodes, two shards and two replicas
using *CloudSolrClient*, is still registering a level of variation in indexing,
please see [http://212.47.227.9/dev/IndexingBenchmarkCloud.html]. This might be
due to the internal mechanism of indexing which could be explained by someone
in our community who may have worked deeply on building/maintaining this
client.
Hi [~michael.sun] Thank you for your appreciation, I am highly motivated and am
looking forward to making this project a success and useful for the community.
I will explore the option that you have recommended and will try to include
that as well for a more meaningful estimation.
Thanks [~ichattopadhyaya] again, for providing me this awesome server to work
on!!!
Regards.
Vivek
> 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
