EnzymeAD / EnzymeAD/ReactantServer.jl

Persistent Kernel Cache

Open
#14 1 comment 0 reactions 0 assignees View on GitHub
enhancement help wanted
Dominant language
Julia
Stars
5
Forks
2
Avg merge
15m
Merged PRs (30d)
10

Description

There are a few issues enabling this currently:

1. It turns on parallel compiliation but nvlink is not bundled with Reactant's CUDA jll
2. There appears to be invalidation issues where a cached kernel is re-used instead of invalidated on change. This leads to issues that appear like buffer aliasing. Need to investigate exactly what is going on here, less confident about the actual diagnosis

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the persistent-kernel-cache path and checking whether Reactant's CUDA jll provides nvlink for parallel compilation. Then investigate cache invalidation when a kernel changes, using the reported buffer-aliasing-like failures as the symptom. Done means parallel compilation works and changed kernels are not incorrectly reused.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
backend, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.