Use of cache_block_id about deepcache HOT 4 CLOSED

Hi @harpavatkeerti

Thanks for your interest in our paper!

cache_block_id corresponds to the n-th residual path in each layer. After defining the cache layer by cache_layer_id, we then choose the n-th residual path within that layer by cache_block_id. As for Stable Diffusion 1.5, the maximum cache_block_id for each layer is 2. Because it is generally divided by different block structures as residuals, we name it cache_block_id.

The name "cache_block_id" seems to cause difficulties in understanding. We would consider to change a name for this. Thanks for your good question!

from deepcache.

Thanks for the clarification @horseee. So, it's a more granular level of control for caching the output of a particular residual path in a layer, if it's the last one, then it's the output of the whole layer, which is detailed in the paper. Else the cache is retrieved from that particular block instead of the previous layer. Is this understanding correct?

from deepcache.

Hi @harpavatkeerti

it's a more granular level of control for caching the output of a particular residual path in a layer

Correct

if it's the last one, then it's the output of the whole layer, which is detailed in the paper

If the U-Net has some middle-layer blocks, then the middle-layer blocks would still not be included by choosing the last path.

Else the cache is retrieved from that particular block instead of the previous layer.

Correct!

from deepcache.

Ok, thanks a lot!

from deepcache.