Investigate compiling code rather than recommending numba for performance

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, python, rust
Domain
performance

Research direction

Start by locating the current performance-sensitive code and its numba usage, then compare the feasibility of C, Cython, or Rust alternatives. Done would require a decided implementation direction and a defined way to verify improved performance without requiring numba.

Written by the indexing model from the issue text.

Description

Describe the feature

numba can be a tricky runtime dependency, it would be good to know if we could write some C/Cython/rust and improve performance for users without them having to use numba

Proposed solution

No response

Dominant language
Python
Stars
16
Forks
8
Avg merge
9h 27m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

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.

More from sunpy/sunkit-magex

All issues in sunpy/sunkit-magex

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.