[ https://issues.apache.org/jira/browse/LUCENE-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531022#comment-17531022 ]
ASF subversion and git services commented on LUCENE-10524: ---------------------------------------------------------- Commit c3d47507e9d312029f7c8fa5166e9a5dfa71d6eb in lucene's branch refs/heads/main from Gautam Worah [ https://gitbox.apache.org/repos/asf?p=lucene.git;h=c3d47507e9d ] LUCENE-10524 Add benchmark suite details to CONTRIBUTING.md (#853) > 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 > Time Spent: 50m > Remaining Estimate: 0h > > 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: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org