thumbnail.exists() is too slow when using S3 as a backend storage

[leotsem]

clearly, it's more a django-storages issue than a sorl issue, but in my case, when using S3 as a backend, it took about 60 secons to run thumbnail.exists() so I've removed the check and made the assumption that if the thumbnail does not exist in the cache it does not exist on the disk either. Now it runs under 1 second.

[tomwys]

I use sorl.thumbnail with S3 (django-storages + s3boto; EC2; Europe) and it works fine (I heven't spotted any delays). Are you sure that this is S3 fault? Maybe it's problem with your server or connection? Do you use EC2 or different server? Do you have S3 and EC2 in same region? How is it possible that checking if thumbnail exists takes 60s, but creating new one and storing to S3 takes under 1s?

[sorl]

"exists() is extremely slow when using S3boto as a backend, so I've make the assumption that if the thumbnail is not cached, it doesn't exist" I am not going to merge that, better use a custom backend if you like - or add option not to check or something.

[mlewis]

If anyone comes across this looking for why easy-thumbnails is so slow with s3boto, it is the same problem. Search for "storage.exists." I had a terrible time trying to find the issue and this was the only page that led me to the answer.

[mariocesar]

There is a possible solution been discuss in #351, to recap this issue is not about sorl-thumbnail itself is about slow storage backends implementations.