Replies: 2 comments 2 replies
-
|
Here's a list of functions which I believe could be a good starting point, either because they are most relevant or because they have a "heavy algorithmic component". Feel free to disagree, I'm certainly biased to the parts of the library I'm most familiar with.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for starting thinking about this Mateo! I like the ideas, and from my brief research it seems that ASV or pytest-benchmark would be the best options (since there are pre-existing examples for both). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, Graphix lacks a systematic way of benchmarking the codebase. #403 is a tentative PR to fill this gap, but this issue demands a deeper examination. The goal of this discussion is to identify our needs, set up a road map and collect useful references.
Basic questions
Which functionality of the codebase do we want to benchmark and on which samples ?
Which benchmarking tool to use ?
Benchmarking frameworks
Airspeed velocity
numpy,scipyandastropy.cProfile.Codspeed
(To be explored)
pytest-benchmark
pyperformance
Additional references
asvasvintegration:Beta Was this translation helpful? Give feedback.
All reactions