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
Hi !
Just had a look on memory consumption after loading dataset. After 3D texture creation I believe we can clean RAM from pixel data namely VolumeDataset.data and some arrays in importer classes. Can be useful especially when loading multiple datasets.
What do you think ?
Regards
The text was updated successfully, but these errors were encountered:
Hi @24THEGuNNeR07,
Thanks for reaching out!
That's a great point! We already remove the texture data from memory (by calling Texture3D.Apply with makeNoLongerReadable set to true, however the VolumeDataset.data is still in memory.
For some uses it is necessary to keep this array in memory, since they may query or modify it, however maybe we could add a setting for automatically clearing it when it's no longer needed? Or alternatively a method for clearing it, and then adding some checks to make sure we don't get errors when we try to access it after it has been cleared.
Hmm not sure what's the case when you need this data in memory can you give some examples ? I would say if it's rare then import them again from file if that would be not suitable because of too often waiting process then I'd leave it as it is and clear it only on importer scripts side.
Hi !
Just had a look on memory consumption after loading dataset. After 3D texture creation I believe we can clean RAM from pixel data namely
VolumeDataset.data
and some arrays in importer classes. Can be useful especially when loading multiple datasets.What do you think ?
Regards
The text was updated successfully, but these errors were encountered: