|
From: | Karl Rasche |
Subject: | Re: [Openexr-devel] EXR texture memory overhead |
Date: | Fri, 16 Sep 2016 11:45:35 -0700 |
But it's not optimal for a use pattern like TextureSystem where the typical request is ONE tile, and the next tile it wants may not even be adjacent.
Wait, I'm not quite sure how threads play into this. Is this allocated framebuffer part of the ImageInptut itself? Do threads lock to use it? Or is this per thread, per file?
[Prev in Thread] | Current Thread | [Next in Thread] |