You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Adrien Grand (Jira)" <ji...@apache.org> on 2022/07/19 21:43:00 UTC

[jira] [Resolved] (LUCENE-10524) Augment CONTRIBUTING.md guide with instructions on how/when to benchmark

     [ https://issues.apache.org/jira/browse/LUCENE-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrien Grand resolved LUCENE-10524.
-----------------------------------
    Fix Version/s: 10.0 (main)
       Resolution: Fixed

> 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
>             Fix For: 10.0 (main)
>
>          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.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org