[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106234#comment-16106234
]
Ishan Chattopadhyaya edited comment on SOLR-10317 at 7/30/17 5:04 PM:
----------------------------------------------------------------------
bq. I have fixed the label bug on graphs. Please see
http://212.47.242.214/MergedViewStandalone.html
Thanks
bq. I will compile and list the TODO items shortly.
What is the status of this? As per GSoC guidelines, a student is expected to
put in about 40 hours of work each week (which is approximately 8 hours a day).
Couldn't you spare 5 minutes from those 8-16 hours (in last 2 days) to get to
this?
I requested you to share the weekly status with the mentors via email (which
you have been doing, even though the level of detail can be improved). Going
forward, can you kindly post the *daily status here in JIRA* and include
sufficient details on work you have done each day? Daily status reporting has
been something that other GSoC projects have benefited from, and I'd like to
try this to ensure that we are on track to complete this project as well as
possible.
bq. The ability to locate and download test data files is awesome and now the
system will be able to check the data file presence and download the missing
file(s) by itself as required. The source URL is configurable through the
properties file.
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].
Your README file says:
{quote}
Test Data Files
* The system has the ability to check and download required data files from
the source, as specified in the properties file.
* If you want to manually download files please use the link provided below.
{quote}
Why are you calling it "test data files"? Also, as a user, I don't fucking care
about what ability the system has. I want information on *how to use whatever
fucking ability the system has*. You need to be specific in terms of steps the
user needs to take.
Secondly, "please use the link provided below" is equivalent to telling the
user to "go f*** yourself". Just provide an exact command that will enable the
user to download those files!
Please understand that if someone is not able to use your system due to poor
documentation or poor interface, then your system is useless to him/her. As of
now, this entire project is useless to anyone except you or me. I urge you to
fix this aspect at the earliest.
[0] - https://da.gd/x0aR
was (Author: ichattopadhyaya):
bq. I have fixed the label bug on graphs. Please see
http://212.47.242.214/MergedViewStandalone.html
Thanks
bq. I will compile and list the TODO items shortly.
What is the status of this? As per GSoC guidelines, a student is expected to
put in about 40 hours of work each week (which is approximately 8 hours a day).
Couldn't you spare 5 minutes from those 8-16 hours (in last 2 days) to get to
this?
I requested you to share the weekly status with the mentors via email (which
you have been doing, even though the level of detail can be improved). Going
forward, can you kindly post the *daily status here in JIRA* and include
sufficient details on work you have done each day? Daily status reporting has
been something that other GSoC projects have benefited from, and I'd like to
try this to ensure that we are on track to complete this project as well as
possible.
bq. The ability to locate and download test data files is awesome and now the
system will be able to check the data file presence and download the missing
file(s) by itself as required. The source URL is configurable through the
properties file.
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].
Your README file says:
{quote}
Test Data Files
* The system has the ability to check and download required data files from
the source, as specified in the properties file.
* If you want to manually download files please use the link provided below.
{quote}
Why are you calling it "test data files"? Also, as a user, I don't fucking care
about what ability the system has. I want information on *how to use whatever
fucking ability the system has*. You need to be specific in terms of steps the
user needs to take.
Secondly, "please use the link provided below" is equivalent to telling the
user to "go f*** yourself". Just provide an exact command that will enable the
user to download those files!
Please understand that if someone is not able to use your system due to poor
documentation or poor interface, then your system is useless to him/her. As of
now, this entire project is useless to anyone except you or me. I urge you to
fix this aspect at the earliest.
[0] - https://paste.fedoraproject.org/paste/TaYvUCH7vSQRdkYGRkmPnQ
> 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,
> Screenshot from 2017-07-30 20-30-05.png, 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
