@@ -1365,16 +1365,16 @@ environments. If you want to use virtualenv instead, write::
1365
1365
The ``-E virtualenv `` option should be added to all ``asv `` commands
1366
1366
that run benchmarks. The default value is defined in ``asv.conf.json ``.
1367
1367
1368
- Running the full test suite can take up to one hour and use up to 3GB of RAM.
1369
- Usually it is sufficient to paste only a subset of the results into the pull
1370
- request to show that the committed changes do not cause unexpected performance
1371
- regressions. You can run specific benchmarks using the `` -b `` flag, which
1372
- takes a regular expression. For example, this will only run tests from a
1373
- ``pandas/asv_bench/benchmarks/groupby.py `` file::
1368
+ Running the full benchmark suite can be an all-day process, depending on your
1369
+ hardware and its resource utilization. However, usually it is sufficient to paste
1370
+ only a subset of the results into the pull request to show that the committed changes
1371
+ do not cause unexpected performance regressions. You can run specific benchmarks
1372
+ using the `` -b `` flag, which takes a regular expression. For example, this will
1373
+ only run benchmarks from a ``pandas/asv_bench/benchmarks/groupby.py `` file::
1374
1374
1375
1375
asv continuous -f 1.1 upstream/master HEAD -b ^groupby
1376
1376
1377
- If you want to only run a specific group of tests from a file, you can do it
1377
+ If you want to only run a specific group of benchmarks from a file, you can do it
1378
1378
using ``. `` as a separator. For example::
1379
1379
1380
1380
asv continuous -f 1.1 upstream/master HEAD -b groupby.GroupByMethods
0 commit comments