-
Notifications
You must be signed in to change notification settings - Fork 7
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
New cahce system. #15
Comments
yes, this is good, if we write the cache inside C code and do not load it at all in Blender or just every few frames it can heavily affect the performance of the code. because at the moment it calculates every single substep for import, export, and load data, and as I can see it will take about 30% of all processing time. if we do all substeps and then just update the viewport at the end of it like what you did in writing the cache we can improve the code massively. |
The only way we can achieve best performance is to save data in the background without using any kind of sending and receiving data in a blender, and complete the detached task, in blender we check if the cache is available for a frame load it if not just skip until it's ready. in this way we can get 95% of CPU to work on the simulation not most of it on blender and just leave small pice on CPU not even a core or thread, the natural idle process for blender UI and loading the cache separately. |
Make a new cache system independent from the blender cache, and add dedicated thread for the cache system.
The text was updated successfully, but these errors were encountered: