PyO3/pyo3

Expand performance section of the guide

Open

#3,310 opened on Jul 11, 2023

View on GitHubContributor guide
 (9 comments) (4 reactions) (0 assignees)Rust (668 forks)batch import
Good First Issue

Repository metrics

Stars
 (10,152 stars)
PR merge metrics
 (PR metrics pending)

Description

  • Overhead of conversions (i.e. PyList vs Vec etc.)
  • String intern!
  • Vec<u8> becoming list[int] (and thus being very slow), usage of Cow<[u8]> as an alternative
  • #[pyo3(get)] deep-cloning non-Py data
  • dictionary dispatch, i.e. look-up based on type object identity

Contributor guide

Research direction
Research each bullet point (e.g., conversion overhead, string intern, Vec<u8> vs Cow<[u8]>, deep cloning from #[pyo3(get)], dictionary dispatch) and provide clear explanations and code examples for the guide's performance section.
Tech stack
rust
Domain
backenddocumentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70