4 ms·
Careful with the zipimport approach to running Django: you may see very high response times for "cold" requests to App Engine. If you can wait, it is likely tha
by davepeck 16y ago
Careful with the zipimport approach to running Django: you may see very high response times for "cold" requests to App Engine. If you can wait, it is likely that GOOG will eventually support Django 1.2 via the use_library() call, which seems to give far better performance.
- tosh 16y agoYou are absolutely right, thank you for the advice. I am going to update the article as soon as django 1.2 is supported via use_library() to reflect this. Cold startup time really is a bummer for low traffic apps.
- davepeck 16y agoYep, cold hits are a pain. They're bad for low traffic apps because App Engine will deallocate all resources if your app hasn't been hit in a while. Interestingly, cold hits are bad for apps with spiking traffic, too: as your load spikes, App Engine tasks new machines each of which may experience a cold hit. (It depends on their caching internals, subject to change.) As for use_library() vs App Engine Patch: for me, the perf issue is primary. On the other hand, AEP offers a lot of functionality out-of-box that you don't get with raw use_library() django.