Hi !
It seems that the Clean Up GPU Memory pulse parameter doesn’t work. When I middle click the mouse button on the concerned operator, it still uses GPU Memory even if it’s not cooking
Hello @schubhan.arv
Which POPs have you seen this issue on?
Thanks
Hello Guillaume,
In this case, every node except Attribute and Null :
I know it happened as well on other networks types, maybe it’s this info popup that isn’t updated but I don’t think so because I see no GPU memory drop after the “Clean Up”
Actually using 2025.30060 on Windows 26100.4061
I9 13900KF
RTX 4080 SUPER
Just to make sure we’re on the same page, here’s how the “Clean up GPU memory” option is supposed to work:
If an operator requires less GPU memory due to changes in a parameter or input, we typically don’t reallocate memory. Instead, the same buffers are used, but they’re filled with less data. Since reallocation can be costly in terms of performance, we avoid doing it frequently. The “Clean up GPU memory” option allows users to manually trigger memory reallocation, enabling the system to use less memory when an operator no longer needs as much.
You can try it on the Sprinkle POP in your example. If you lower the number of points and hit “Clean up GPU memory”, you should see a difference.
Oh okay the word “Clean” makes sense now. Is it possible to add a “Free GPU Memory” or maybe a function like the TOP unload() ? It’s very important for realtime performances
I agree, the name wasn’t entirely appropriate. We’ll probably change it and go with “Free Extra GPU Memory”. In Python, we currently have the reallocate() method.
Okay thank you for everything !