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

Yicong Huang updated SPARK-56011:
---------------------------------
    Description: 
Running PySpark ASV benchmarks currently requires changing to the 
{{python/benchmarks}} directory first, which is inconvenient for developers who 
frequently run benchmarks during development.

A wrapper script under {{dev/}} (similar to {{dev/lint-python}}) would allow 
running benchmarks directly from the Spark root directory.

  was:
Currently, running PySpark ASV benchmarks requires changing directory to 
python/benchmarks first:

{code}
cd python/benchmarks
asv run --python=same --quick
{code}

This is inconvenient. Add a {{dev/asv}} wrapper script so benchmarks can be run 
directly from the Spark root directory:

{code}
./dev/asv run --python=same --quick
{code}

This is consistent with other dev scripts like {{dev/lint-python}}.

        Summary: Support running PySpark ASV benchmarks from the repo root 
directory  (was: Add dev/asv wrapper script to run PySpark benchmarks from repo 
root)

> Support running PySpark ASV benchmarks from the repo root directory
> -------------------------------------------------------------------
>
>                 Key: SPARK-56011
>                 URL: https://issues.apache.org/jira/browse/SPARK-56011
>             Project: Spark
>          Issue Type: Improvement
>          Components: PySpark
>    Affects Versions: 4.2.0
>            Reporter: Yicong Huang
>            Priority: Major
>
> Running PySpark ASV benchmarks currently requires changing to the 
> {{python/benchmarks}} directory first, which is inconvenient for developers 
> who frequently run benchmarks during development.
> A wrapper script under {{dev/}} (similar to {{dev/lint-python}}) would allow 
> running benchmarks directly from the Spark root directory.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to