Django在GoogleAppEngine - 性能？ [英] Django on GoogleAppEngine - Performance?

问题描述

在GoogleAppEngine上运行Django，而不是默认的WebApp2框架，会消耗额外的资源？任何指标？

解决方案

从邮件列表中，我看到有关Django实例的多个注释需要更长时间才能启动，如果冷。如果您的应用很少使用，这将是显而易见的。

从我的应用程序的日志中，看起来第一个请求大约需要4秒钟才能启动。

我的Django实例使用41-43MB。不确定webapp2。

如果您使用Django-nonrel作为ORM，我相信在ORM翻译中花费了几个周期，但我怀疑它是重大。对于相同的请求，我的Tastypie REST层可以在40-120ms之间，看起来数据存储的性能比其他任何事情都要多。

Does running Django on GoogleAppEngine, as opposed to the default WebApp2 framework, consume additional resources? Any metrics?

解决方案

From the mailing list, I've seen multiple comments on Django instances taking significantly longer to start up if cold. This would be noticeable if your app is rarely used.

From my app's log it looks like the first request took about 4 seconds to start up.

My Django instances use 41-43MB. Not sure about webapp2.

If you're using Django-nonrel as an ORM, I'm sure there's a few cycles spent in the ORM translation, but I doubt it's significant. My Tastypie REST layer can take anywhere between 40-120ms for the same request, it looks like that performance is dictated more by the datastore than anything else.

这篇关于Django在GoogleAppEngine - 性能？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！