jdinh wrote:I read in the FAQs that SLI is advised to be disabled for performance hits. Is that not the case anymore?
If your card supports NVLink and you have an NVLink bridge installed then its probably wise to have SLI turned on for memory pooling
. Good question as to whether it has a performance hit without actually pooling the memory though (small scene for example)
I have been told on some other hardware related message boards, its not "memory pooling", what is going on with Octane and RTX Geforce cards. Apparently the memory pooling is it only in case of Titan/Quadro cards, where the operating system itself sees their memory buffers as single large one. In case of Octane its peer-to-peer, where the data from one card is copied into memory of the second card.
It may seem like a technicality, and ultimately of no relevance for us as end users, since we get larger memory at our disposal either way, but i have to wonder about those little pesky details, since they can be fairly significant... so does this mean, that in case of Octane, if you have large scene and that P2P kicks in, is then data from the second card copied into the frame buffer of the first card? Thus only one card is doing rendering at that point and the other one is just used as a memory storage accessed via NV-Link (with faster access time than if the data were stored in system RAM, as it the case of OOC?) Or do both card still do the rendering? And what about Quadro/Titan RTX, since these have that "real" memory pooling ability, does NV-Link feature work different for them in Octane?
Would love to have some light shed on this by the devs, since it is truly interesting and nobody in the community seems to have any clue, what is really going on.