Skip to content

task: pin NUMBA_NUM_THREADS=1 in profiling cells + re-measure the DelaunayNN numba Optimal cell - #90

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/numba-threads-profiling-followup
Nov 5, 2026
Merged

Jammy2211 merged 1 commit into
mainfrom
feature/numba-threads-profiling-followup

Conversation

@Jammy2211

Copy link
Copy Markdown
Contributor

Summary

Files one profiling task (measurement-tools campaign): tasks/numba_num_threads_pin_and_delaunay_nn_remeasure.md plus its campaigns.yaml row and the regenerated board.

autolens_profiling/_production_config.pin_thread_env pins BLAS/OMP threads but not NUMBA_NUM_THREADS, and numba ignores OMP_NUM_THREADS. So the day-zero optimal cell imaging/delaunay_nn/hst numba_cpu_sparse_fp64@hpc_ral_cpu ran its then-always-parallel Sibson kernel on up to 8 cores. On the laptop at the profiled size, Sibson takes 14 ms with 8 threads and 56 ms with 1, about 3–10% of the 1.3 s call. Production workers are single-core and, since PyAutoArray#677, always serial.

Steps:

  1. Pin NUMBA_NUM_THREADS (no compute).
  2. Re-measure after the release carrying #677 (RAL go needed).
  3. A human decision on the day-zero designation.

No other numba cell is affected; the task lists why.

Test Plan

  • bin/pyauto-pulse board --offline (board gains one open-task line only)
  • bin/pyauto-pulse check --offline: OK

🤖 Generated with Claude Code

…NN numba Optimal cell after PyAutoArray#677

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Jammy2211
Jammy2211 merged commit a57e1b2 into main Nov 5, 2026
2 checks passed
@Jammy2211
Jammy2211 deleted the feature/numba-threads-profiling-followup branch November 5, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant