-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Value Clips memory usage grows with the square of the number of "times" entries #1774
Comments
Filed as internal issue #USD-7222 |
Hey @marktucker - oof, we've never exercised the explicit form to that scale; good find! Your approach seems to us like the right thing, and we'd be happy to get a PR. |
Hey @jilliene / @spiffmon, We (at RISE | Visual Effects Studios) were wondering what the current state of the attached PR from Mark is? Has it been reviewed/are there plans to merge it soon (#1777)? Thanks again Mark for submitting the PR :) We've been running into this issue quite often for heavy FX scenes, the fix would help us quite a bit if it gets released soon :) Cheers, |
Hi @LucaScheller , although it hasn't been pushed out to gitHub yet, I believe we merged the PR just last week, so it will be in the dev branch soon, and in the next release, tentatively 22.08 |
Thanks for the update, that's great to hear :) |
PR #1777 was merged and released in 22.08, closing this out. Thanks! |
Description of Issue
If you create a value clip with 15000 "times" entries, the Usd_Clip data structures consume about 5GB of data, regardless of the size of the data in the actual clip files.
This memory if consumed by the fact that each Usd_Clip object makes a copy of the 15000-entry timeMapping array created in the Usd_ClipSet constructor. I think each Usd_Clip applies the same sorting procedure to the data, and makes it's own copy. Seems like the obvious solution would be to have the Usd_ClipSet constructor massage the data, then pass a shared pointer to each Usd_Clip constructor. I'd be happy to make a PR for this if you think this is the correct approach to fixing this.
Steps to Reproduce
value_clip_memory.zip
Package Versions
Tested in 20.08, 21.08, and 21.11
The text was updated successfully, but these errors were encountered: