feat: Add dedicated GitHub Actions Performance Benchmarking workflow#30
Merged
feat: Add dedicated GitHub Actions Performance Benchmarking workflow#30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR introduces a dedicated, standalone GitHub Actions workflow (
.github/workflows/benchmark.yml) designed to automatically benchmark Apple MLX generation speeds directly on the CI infrastructure (macos-15runner).Since Cloud macOS runners typically possess exactly 7 GB of RAM, blindly running the standard benchmark script matrix risks immediate Out-Of-Memory (OOM)
SIGKILLboundaries. This safe workflow explicitly forces constraints and exposes a configurable matrix to test safe parameter bounds directly from the UI.Features
workflow_dispatch): Fully configurable directly through the GitHub Actions web UI. Does not run implicitly on pushes.model_idinput immediately prior to run. Defaults to the un-gatedmlx-community/gemma-4-e4b-it-4bitwhich safely drops into memory constraints."512,1024,4096") by default.--ssd-onlyparameter to explicitly bypass physical limits and test extreme combinations.Outputs
mlx,psutil,requests) inside the GH Action.github-action-benchmark.mdtable securely as an exported execution artifact on each run.