Option Request ?

Started by joshbakr, March 08, 2008, 12:04:58 PM

Previous topic - Next topic

joshbakr

Does anyone think a "Purge Memory" Option would come in handy in future versions?  Reason for my question is: I've been working with Vue6 for a few months and this option seems to help free memory just before starting a render. Rather than saving the scene, closing the software and sometimes rebooting the system before starting a render. Hope I explained it correctly.

reck

I think options like this should not be displayed to the end user and should be managed by the software in the background automatically. As users we should should just be concerned with using the software for what it was designed for and not have to worry about having to free memory etc, memory management should be a function of the software, not the end user. My 2p worth.

rcallicotte

@joshbakr - I agree.  Either having this option or, as reck explained, having the software do it for us seems reasonable.  I think these sorts of things are what optimization is all about, once the program is actually doing what it was designed to do.  Let's hope for this and a lot more.
So this is Disney World.  Can we live here?

Seth

Quote from: joshbakr on March 08, 2008, 12:04:58 PM
Does anyone think a "Purge Memory" Option would come in handy in future versions?  Reason for my question is: I've been working with Vue6 for a few months and this option seems to help free memory just before starting a render. Rather than saving the scene, closing the software and sometimes rebooting the system before starting a render. Hope I explained it correctly.

I totally agree with this proposition !
I always save and exit before restarting TG2 to render a final pic... and it's not a pleasant way to work...

jaf

I see it this way.  Any application should purge memory whenever a "new" or no "undo" situations exist.  Of course "undo" will vary with the application (like loading a different image shader).  So a stopped render should free any memory used when the render function is started.   But for efficiency, a "generate terrain" should not be "undo-able".  But the developer should be able to decide what can be reasonably "undone" and still keep the memory requirements reasonable.
(04Dec20) Ryzen 1800x, 970 EVO 1TB M.2 SSD, Corsair Vengeance 64GB DDR4 3200 Mem,  EVGA GeForce GTX 1080 Ti FTW3 Graphics 457.51 (04Dec20), Win 10 Pro x64, Terragen Pro 4.5.43 Frontier, BenchMark 0:10:02

Mr_Lamppost

Even if an application is optimised to purge memory etc. I still have a habit of saving my work and closing down my computer completely then starting from scratch before a big final render.  1 guess what sorry excuse for an operating system I am using.  ???
Smoke me a kipper I'll be back for breakfast.

Oshyan

Ideally such a function shouldn't be necessary - the app should handle memory management properly in an automatic fashion. Purging undo caches is the only common application feature I see in high-end apps like this, and even that is rare. Improving memory management is definitely on the list of future enhancements though.

- Oshyan