Skip to content

Need a holistic approach to file I/O for benchmarks #1698

Closed

Description

@cmdupuis3

This issue is two-pronged:

  1. File I/O for benchmarks is implemented on a per-benchmark-file basis, so it's difficult to know at a glance which files are currently being used for benchmarks. This also promotes copy-pasting of I/O code, so consolidating the I/O would be in line with the DRY principle.
  2. Partly as a consequence of (1), the fragmented I/O regime basically makes ASV retrieve the needed files at every single benchmark run. For benchmark suites on shared files, this can be enormously expensive.

Instead, I'm proposing that we have one benchmark helper file to support all needed file I/O, which will consolidate I/O code and enable single-retrieval for batches of benchmarks.

Activity

  1. self-assigned this
    on Aug 20, 2026
  2. added
    benchmarkingRelated to benchmarks, memory usage, and/or time profiling
    on Aug 20, 2026
  3. moved this from 📚 Backlog to 📝 To-Do in UXarray Developmenton Aug 20, 2026
  4. moved this from 📝 To-Do to 🏗 In progress in UXarray Developmenton Aug 21, 2026
  5. moved this from 🏗 In progress to 👀 In review in UXarray Developmenton Sep 22, 2026
  6. moved this from 👀 In review to ✅ Done in UXarray Developmenton Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

benchmarkingRelated to benchmarks, memory usage, and/or time profilingscalabilityRelated to scalability & performance efforts

Type

No type

Fields

Priority

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions