ZereneStacker memory
Moderators: rjlittlefield, ChrisR, Chris S., Pau
ZereneStacker memory
Not sure if this has been asked before - could not find anything on a quick search - but is there benefit to ZereneStacker increasing memory in the application itself from say 12GB to 30GB if you have the physical RAM? Will it run faster? Or is it already CPU bound at 12GB?
- rjlittlefield
- Site Admin
- Posts: 23562
- Joined: Tue Aug 01, 2006 8:34 am
- Location: Richland, Washington State, USA
- Contact:
It's CPU bound at well below 12 GB.
At the present time, there's really no advantage in giving ZS much more than about 100 bytes per pixel, for example 2100 MB (2.1 GB) for 21 megapixels.
The optimum allocation will probably grow in the future as the software evolves to productively use more memory. But at the present time, giving ZS more memory just takes it away from other processes without doing ZS much good. More memory does make ZS run very slightly faster, but the improvement is so small that it's hard to measure against the background variation in run time caused by operating system caching and random variations in thread timing and garbage collection within ZS.
--Rik
At the present time, there's really no advantage in giving ZS much more than about 100 bytes per pixel, for example 2100 MB (2.1 GB) for 21 megapixels.
The optimum allocation will probably grow in the future as the software evolves to productively use more memory. But at the present time, giving ZS more memory just takes it away from other processes without doing ZS much good. More memory does make ZS run very slightly faster, but the improvement is so small that it's hard to measure against the background variation in run time caused by operating system caching and random variations in thread timing and garbage collection within ZS.
--Rik