Out-of-core textures allow users to use more textures than would fit in the graphic memory, by keeping them in the host memory. The data for rendering the scene needs to be sent to the GPU while rendering so some tradeoff in the rendering speed is expected. If out-of-core textures are not used, however, the rendering speed is not affected. Note also that OctaneRender’s Out-Of-Core settings is only for textures, not geometry or render buffers.
Out-of-core textures also come with another restriction: They must be stored in non-swappable memory which is limited. So when the host memory is used up for out-of-core textures, bad things will happen since the system can not make room for other processes. Since out-of-core memory is shared between GPUs, users also can not turn devices on or off while using out-of-core textures.
Users can enable and configure the out-of-core memory system via the application preferences. For net render slaves, users can specify the out-of-core memory options during the installation of the daemon.