You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Antoine Pitrou (JIRA)" <ji...@apache.org> on 2018/01/31 13:18:00 UTC
[jira] [Commented] (ARROW-1861) [Python] Fix up ASV setup, add
developer instructions for writing new benchmarks and running benchmark
suite locally
[ https://issues.apache.org/jira/browse/ARROW-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346791#comment-16346791 ]
Antoine Pitrou commented on ARROW-1861:
---------------------------------------
Is there a point in testing so many different sizes in the benchmarks? Intuitively I would test two different sizes ("small" and "large" e.g. 10 and 1e6). More sounds overkill
> [Python] Fix up ASV setup, add developer instructions for writing new benchmarks and running benchmark suite locally
> --------------------------------------------------------------------------------------------------------------------
>
> Key: ARROW-1861
> URL: https://issues.apache.org/jira/browse/ARROW-1861
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 0.9.0
>
>
> We need to start writing more microbenchmarks as we go to prevent unintentional performance regressions (this has been a constant thorn in my side for years: http://wesmckinney.com/blog/introducing-vbench-new-code-performance-analysis-and-monitoring-tool/).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)