Skip to content

[bench] Pilot CCCL Runtime usage in one benchmark family #9575

Description

@pciolkosz

Part of #2800.

Pilot CCCL Runtime usage in one narrow benchmark family.

Pick one benchmark directory/family after review, then apply Runtime APIs comprehensively within that small semantic batch.

Keep benchmark work separate from test migrations. Be careful not to disturb timing semantics unless the timing/event migration is explicitly part of the batch.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status
Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions