benchmarks: benchmark cupy

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
performance

Research direction

The issue provides no file, test, benchmark entry point, or acceptance criteria. Start by locating the repository's existing benchmark setup and determine how a CuPy benchmark should be represented; done means the intended CuPy benchmark is added and its results can be run and compared.

Written by the indexing model from the issue text.

Description

component: benchmark type: cupy

This issue has no description.

Dominant language
Python
Stars
15
Forks
5
Avg merge
10h 33m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

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 scverse/fast-array-utils

All issues in scverse/fast-array-utils

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.