Skip to content

test(qudarap): cap max_slot in QEvt_Lifecycle_Test to avoid VRAM OOM#354

Open
ggalgoczi wants to merge 1 commit into
mainfrom
fix-qevt-lifecycle-maxslot
Open

test(qudarap): cap max_slot in QEvt_Lifecycle_Test to avoid VRAM OOM#354
ggalgoczi wants to merge 1 commit into
mainfrom
fix-qevt-lifecycle-maxslot

Conversation

@ggalgoczi
Copy link
Copy Markdown
Contributor

QEvt_Lifecycle_Test left max_slot at the default (0), which SEventConfig:: SetDevice sizes to a fraction of total VRAM (~192M slots / ~12 GB on a 24 GB card). On a shared or otherwise occupied GPU that allocation OOMs in QEvt::device_alloc_photon, making the test flaky in CI. The test only processes the 10k input photons in RainXZ_Z230_10k_f8.npy, so cap max_slot at 1M (~64 MB), which is deterministic and independent of GPU occupancy.

QEvt_Lifecycle_Test left max_slot at the default (0), which SEventConfig::
SetDevice sizes to a fraction of total VRAM (~192M slots / ~12 GB on a
24 GB card). On a shared or otherwise occupied GPU that allocation OOMs in
QEvt::device_alloc_photon, making the test flaky in CI. The test only
processes the 10k input photons in RainXZ_Z230_10k_f8.npy, so cap max_slot
at 1M (~64 MB), which is deterministic and independent of GPU occupancy.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant