main

Warming up the performance wizard...

Python 3.13 project (uv), pytest suite, depends on bpy

Analyze repository

Rebased onto the CodSpeed setup that landed on main; added 10 parsing-layer benchmarks

Set up pytest-codspeed benchmarks

All benchmarks reported in simulation mode

Run benchmarks locally with CodSpeed

Reusing the CodSpeed workflow already on main

Add CodSpeed GitHub Actions workflow

PR #1270: CodSpeed run succeeded, bot reported 10 new benchmarks

Open PR and monitor CI

Benchmarks have been successfully run and processed. The results are available in Codspeed

Processing benchmark results

PR #1270 (https://github.com/BradyAJohnston/MolecularNodes/pull/1270) adds 10 new CodSpeed benchmarks. The CodSpeed workflow passed on it, and the CodSpeed bot commented that it found 10 new benchmarks and that performance doesn't change.

While I was working on this, your own CodSpeed setup landed on `main` in commit 68f0f8c, with its own workflow, `benchmarks/conftest.py`, and benchmarks for loading molecules, trajectories and evaluating styles. My first version clashed with it, so I rebased and narrowed the PR to things that add to your setup:

- **New file `benchmarks/test_parsing.py`:** benchmarks for the Python parsing code that runs inside `mn.Molecule.load` before any Blender data exists:
  - `read_structure` for `.bcif`, `.cif`, `.pdb` and `.sdf` files
  - `set_standard_annotations`
  - `color_chains`
  - building biological assemblies from mmCIF and PDB files
  - `selections.from_string`

  It uses the existing conftest and the test data already in `tests/data`, so nothing is downloaded. Your workflow, conftest and dependencies are not changed.
- **README:** a CodSpeed badge next to the CI badge.

The CI workflow fails on this PR's commit: 10 test jobs failed. In the Ubuntu bpy job I checked, the only error was a connection timeout in `test_emdb_api_density_load` while downloading a density map from ftp.ebi.ac.uk. I didn't look at the logs of the other nine jobs, so I can't confirm they failed for the same reason. CI also failed on the latest commits of two of your branches (`perf-load-speedups` and `perf-batch-asset-linking`).

I've requested your review and marked the PR ready.

Performance History

Latest Results

Latest Branches