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
So my usecase is currently a semi-realtime meshing of fluids from salva; for around 1k particles, I'm able to mesh about every 30-60ms.
As apart of perf investigations, I'm wondering if we can reduce some of this overhead by providing a vertices and indices out param, perhaps something like:
So your idea would be to basically call .clear() on them and just reuse the reserved capacity? Maybe you can try it out to see how this affects performance in your case. I would be open to merge it.
I have a patch doing this which does not change the current api; i can push it. Yea so with out params like that the idea is that you only get the allocation hit once or twice so memory use becomes stable after running for a while (it keeps writing into same heap storage)
So my usecase is currently a semi-realtime meshing of fluids from salva; for around 1k particles, I'm able to mesh about every 30-60ms.
As apart of perf investigations, I'm wondering if we can reduce some of this overhead by providing a vertices and indices out param, perhaps something like:
This should reduce some pressure on the allocator?
The text was updated successfully, but these errors were encountered: