[
https://issues.apache.org/jira/browse/LUCENE-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525214#comment-17525214
]
Gautam Worah commented on LUCENE-10524:
---------------------------------------
I have a slight personal preference towards using/reading Markdown files (a
gradle command for instructions about benchmarking feels a bit obtuse) but a
gradle command also sounds nice (and fits the general pattern in Lucene). It
may take me some time to start working on this issue (~3 days) but I'll get
back with a PR!
> Augment CONTRIBUTING.md guide with instructions on how/when to benchmark
> ------------------------------------------------------------------------
>
> Key: LUCENE-10524
> URL: https://issues.apache.org/jira/browse/LUCENE-10524
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Gautam Worah
> Priority: Minor
>
> This came up when I was trying to think about improving the experience for
> new contributors.
> Today, new contributors are usually unaware of where luceneutil benchmarks
> are and when/how to run them. Committers usually end up pointing contributors
> to the benchmarks package when they make perf impacting changes and then they
> run the benchmarks.
>
> Adding benchmark details to the Lucene repo will also make them more
> accessible to other researchers who want to experiment/benchmark their own
> custom task implementation with Java Lucene.
>
> What does the community think?
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
