MKLab-ITI / MKLab-ITI/pygrank

Autotune too slow for backends other than numpy

Open
#20 0 comments 0 reactions 1 assignee View on GitHub

@maniospas is already working on this.

Since Jan 13, 2023.

enhancement
Dominant language
Python
Stars
28
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Investigate why filter tuning can be exceptionally slow for backends other than numpy.

  • Focus on matvec first.
  • Slowness persists when L1 is used as optimization measure instead of AUC for matvec, investigate potentially slow operations (e.g., indexing?) in that project.

Related tests: None (change backends in the current compare_filter_tuning.py in the playground)

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.