uwsgi + django 缓慢重生/重新加载/重新启动

Question

我在 debian jessie 上使用 django 1.7.7 和 uswgi 2.0.7

Uwsgi 重生/重新加载/重新启动非常慢。似乎达到了超时（30s）。

Fri Jul 31 08:20:59 2015 - SIGINT/SIGQUIT received...killing workers...  
Fri Jul 31 10:21:29 2015 - *** Starting uWSGI 2.0.7-debian (64bit) on [Fri Jul 31 10:21:29 2015] ***

Fri Jul 31 09:25:53 2015 - SIGINT/SIGQUIT received...killing workers...  
Fri Jul 31 11:26:24 2015 - *** Starting uWSGI 2.0.7-debian (64bit) on [Fri Jul 31 11:26:24 2015] ***

我有两个版本的 uwsgi ini 文件的问题。首先像描述（django doc）：

 # Django's wsgi file
 module          = ntbserver.wsgi:application

并像这里描述的那样（uwsgi doc）

# Django's wsgi file
module          = ntbserver.wsgi

我在turorials中找到了第三个版本。如果我这样做：

# Django's wsgi file
module          = django.core.handlers.wsgi:WSGIHandler()

这是瞬时的

Fri Jul 31 11:25:46 2015 - SIGINT/SIGQUIT received...killing workers...  
Fri Jul 31 11:25:47 2015 - worker 1 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 2 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 3 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 4 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 5 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 6 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 7 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 8 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 9 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - worker 10 buried after 1 seconds
Fri Jul 31 11:25:47 2015 - goodbye to uWSGI.
Fri Jul 31 11:25:47 2015 - VACUUM: pidfile removed.
Fri Jul 31 11:25:47 2015 - VACUUM WARNING: unix socket /run/uwsgi/app/ntbserver/socket changed inode. Skip removal
Fri Jul 31 11:25:48 2015 - *** Starting uWSGI 2.0.7-debian (64bit) on [Fri Jul 31 11:25:48 2015] ***

但是，我不明白这种变化的区别和影响。我找不到相关的文档或建议。如果有人可以帮助我。