This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
test.out_of_memory_recovery is extremely slow #1183
Assignees
Comments
alliepiper
added a commit
to alliepiper/thrust
that referenced
this issue
Jun 9, 2020
Fixes NVIDIA#1183. This test is taking up the majority of the test runtime on CPU backends, slowing eating away at RAM/swap for two minutes while the rest of the system gets evicted from RAM and stops responding. Replaced the allocation loop with a single large allocation, now the test runs in ~1ms and doesn't actually allocate significant resources.
alliepiper
added a commit
that referenced
this issue
Jun 10, 2020
Fixes #1183. This test is taking up the majority of the test runtime on CPU backends, slowing eating away at RAM/swap for two minutes while the rest of the system gets evicted from RAM and stops responding. Replaced the allocation loop with a single large allocation, now the test runs in ~1ms and doesn't actually allocate significant resources.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This test takes about a minute and a half to run on a system with 32GB RAM + 32GB swap, and it renders the system unresponsive for most of that time as it slowly allocates the entire 64 GB of available memory, thrashing all other processes. We should look into ways to speed this up and play nice with other processes.
The text was updated successfully, but these errors were encountered: