dateutil/dateutil

Profiling

Open

#505 opened on Nov 8, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (2,189 stars) (470 forks)batch import
enhancementhelp wantedmedium-difficultytests

Description

We should put together a standardized profiling suite. The pandas folks use asv, not sure what other options they considered.

Tangentially related: @pganssle when running afl the other day, did you put together something to run through various input options? I poked at it long enough to get to the curses screen but not enough to pull anything meaningful out of the results.

Contributor guide

Tech stack
python
Domain
performance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Python profiling toolsairspeed velocity (asv)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The issue proposes setting up a standardized profiling suite for dateutil. Research should investigate using `asv` (airspeed velocity) as mentioned, and possibly fuzzing tools like `afl` for performance benchmarking. Look at existing profiling setups in similar projects (e.g., pandas) and evaluate the effort required to integrate such a suite into dateutil's CI. The issue has no assigned person or linked PRs, so the first step is to clarify the scope and decide on specific tools and metrics.