Warning: file_get_contents(/data/phpspider/zhask/data//catemap/2/django/24.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Python uwsgi&x2B;django缓慢恢复/重新加载/重新启动_Python_Django_Uwsgi - Fatal编程技术网

Python uwsgi&x2B;django缓慢恢复/重新加载/重新启动

Python uwsgi&x2B;django缓慢恢复/重新加载/重新启动,python,django,uwsgi,Python,Django,Uwsgi,我在debian jessie上使用django 1.7.7和uswgi 2.0.7 Uwsgi重新启动/重新加载/重新启动的速度非常慢。它似乎达到了一个超时(30秒) 我有两个版本的uwsgi ini文件的问题。第一: 第二 我在turorials中找到了第三个版本。如果我这样做: # Django's wsgi file module = django.core.handlers.wsgi:WSGIHandler() 它是瞬间的 Fri Jul 31 11:25:46 2

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

Uwsgi重新启动/重新加载/重新启动的速度非常慢。它似乎达到了一个超时(30秒)

我有两个版本的uwsgi ini文件的问题。第一:

第二

我在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] ***

但是,我不理解这种变化的区别和影响。我找不到关于这方面的文件或建议。如果有人能帮助我。

我刚刚注意到如果我使用“django.core.handlers.wsgi:WSGIHandler()”;我没有了。如果我启用uwsgi的选项“懒惰的应用程序”,效果会更好,但我不知道确切的原因。我自己仍在思考这个问题,但这里有一些关于“懒惰”概念的解释:
# Django's wsgi file
module          = ntbserver.wsgi
# 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] ***