shake 5k render failed..... how to tweak the speed ?

[selvag]

hi...

i am doing 5k shot ... shake is very slow in processing ... how can i tweak the cache settings...when i tried with shell render its quits "memory allocation failed".
so i tried with network render...it's works fine...

how can i get ride of this problem.

thanks in advance...

[DavidW]

You've hit a restriction in the 32-bit Shake binary. Your comp needs more ram than you got (read: can allocate). This is a problem you can't get round because Shake will only be able to allocate 2Gb RAM (it doesn't matter if you got 4Gb physical memory, one process can still only access 2Gb itself).
The workaround is to alter you comp to use less memory by splitting it up into several precomps or similar...

These problems go away when we all use 64-bit apps in the future!
Cheers, D.

[yukon_28]

Those 3Gb switch trick does not works in shake? (AFAIK its allows to use 3gb of ram on x32 machines with 4gb of ram by switching normal OS/process 2gb/2gb to 1gb/3gb)

[beaker]

from page 131 in the manual which I found quite fast with a search:

Adjusting the Cache for High-Resolution Images
When working with high-resolution images, it’s also necessary to adjust the cache
settings. By default, only images under 2K resolution are cached. By not automatically
caching large files, Shake conserves cache capacity, enabling you to add more files. You
can override this default with the following two lines, which adjust the default values.
The first line sets the maximum size by listing the X resolution, Y resolution, number of
channels, and amount of bytes. The second line sets the maximum amount of disk
space for the cache directory. You can assume that if you are working on 6K plates, you
can allow for more than 512 MB of disk space for your cache. These lines go in your
startup preference files. You modify the numbers to suit your production situation:
diskCache.cacheMaxFileSize = 2048*2048*4*2;
diskCache.cacheSize = 512;
Keep in mind that if you set your maximum file size to 6K x 6K x 4 channels in float, you
are saving massive files. The return you have on swapping this in and out of cache is
extremely limited, at best. It is recommended you use proxies when interactively
working with 4K and 6K images.
If you need to work at full resolution, try putting a Crop at the end of the chain to focus
on an area of interest, or using the Viewer DOD. This retains full pixel resolution, but
keeps your image resolution within the framework of your computer.