running out of memory about densenet HOT 3 CLOSED

The DenseNet models require tons of memory. However, I was able to train the model on a 980M with 4GB of GPU memory, on Theano, with garbage collection enabled to allow for such a large model to run.

I don't see a reason why TF should run out of memory with 8 GB gpu ram, but then I also experienced an OOM when I used the TF backend with 4GB of ram. Perhaps, 4GB is simply not enough to load such a model without GC. When I dropped the batch size to 16 instead of 64, it seemed to work at about the same speed as theano for me.

As to the ImageNet version, I think the model trained on imagenet was the Bottleneck Compressed version of the networks, which have a similar number of parameters (especially the DenseNet-BC-190-40). The authors do mention that they use a batch size of 128 for ImageNet due to GPU memory constraints (see page 7 of the paper, just a bit above the Discussion paragraph), but I do not understand how they can accomplish this on a single GPU (I doubt even a Titan X with 12GB gpu memory can handle this model with such a large batch size for ImageNet images (224x224)).

from densenet.

Hmm, okay good to at least know you've seen something similar. Perhaps if they had 8x titan X machines it might be achievable, assuming a single batch can be distributed across GPUs. The last author is at Facebook so it is conceivable, though I'd expect an imagenet network to be much larger.

from densenet.

Almost all ImageNet results are generally tested on multiple GPU systems, dut to the 1.2 million images taking several weeks on even the most powerful GPUs.

DenseNets definitely are an efficient architecture in comparison to ResNets, but the author's show that the performance of even the largest DenseNet -161 with k=48 has a top 1 accuracy of approximately 78%, whereas Inception ResNet V2 surpasses that at 80.4%, albeit at the cost of a very large number of parameters.

from densenet.