You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't fully understand the BufferAssignment OOM Debugging information when an out-of-memory issue happens. After searching for a while, I didn't find any explanation in the documentation. (Especially, what is maybe_live_out allocation?)
(Also, I assume my program should only require memory for an array of size [42994,42994] but it seems something is wrong. As from theBufferAssignment stats, there seem to be at least two such arrays and it tried to allocate the third one. I guess it's something I misunderstood in adding the arrays by broadcasting #18905. Have to figure it out once I understand the output stats and Peak buffers better.)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I don't fully understand the
BufferAssignment OOM Debugging
information when an out-of-memory issue happens. After searching for a while, I didn't find any explanation in the documentation. (Especially, what ismaybe_live_out allocation
?)Could you explain the following output? Thanks!
(Also, I assume my program should only require memory for an array of size [42994,42994] but it seems something is wrong. As from the
BufferAssignment stats
, there seem to be at least two such arrays and it tried to allocate the third one. I guess it's something I misunderstood in adding the arrays by broadcasting #18905. Have to figure it out once I understand the output stats andPeak buffers
better.)Beta Was this translation helpful? Give feedback.
All reactions