godofecht / godofecht/flow-scikit

[Bench #478] Qualify performance on Linux x86-64 and macOS arm64 without cross-hardware false regressions

Open
#495 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2
Forks
0
Avg merge
4h 33m
Merged PRs (30d)
9

Description

Parent: #478

Current canonical evidence is environment-keyed, but optimization claims need to survive both Tier-1 Flow platforms. BLAS/LAPACK implementation, vector width, compiler and allocator differences can reverse small wins.

Run canonical operation-level and selected scaled benchmarks on Linux x86-64/OpenBLAS and macOS arm64/Accelerate with pinned threads. Maintain independent baselines per environment; never compare absolute timings across machines.

Acceptance: every canonical loss/win has per-platform status; regressions are evaluated only within matching environment IDs; platform-specific holes become explicit child issues; Pages can filter by platform; target #478 eventually has zero material losses on both supported performance platforms.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with parent issue #478 and locate the canonical operation-level and selected scaled benchmarks referenced there. Run them on Linux x86-64/OpenBLAS and macOS arm64/Accelerate with pinned threads, then maintain separate environment-keyed baselines and verify that Pages can filter by platform. Done means every canonical result has a per-platform status and no cross-machine timing comparisons are used.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, macos, python
Domain
infrastructure, performance, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.