resourceCacheSingleAllocationByteLimit

When the cachable entry is very large (e.g. a large scaled bitmap), adding it to the cache can cause most/all of the existing entries to be purged. To avoid this, the client can set a limit for a single allocation. If a cacheable entry would have been cached, but its size exceeds this limit, then we do not attempt to cache it at all.

Zero is the default value, meaning we always attempt to cache entries.