CherryPy 服务器使用线程来处理请求。我的线程服务器中的一种特定方法非常复杂且占用大量 CPU,因此我必须从方法请求线程内部使用多处理来并行化执行。
我以为我只是更换
class Server(object)
@cherrypy.expose
def expensive_method(self):
...
x = map(fnc, args)
...
def fnc(args):
# this method doesn't need CherryPy but is expensive to compute
...
cherrypy.quickstart(Server())
(效果很好)与
def expensive_method(self):
pool = Pool()
x = pool.map(fnc, args)
pool.terminate()
但这不起作用。即使在更简单的情况下,当我根本不使用游泳池时,
def expensive_method(self):
pool = Pool()
x = map(fnc, args) # <== no pool here! same as the working example
pool.terminate()
我得到一个例外
[08/Jan/2013:20:05:33] ENGINE Caught signal SIGTERM.
2013-01-08 20:05:33,919 : INFO : _cplogging:201 : error(CP Server Thread-3) : [08/Jan/2013:20:05:33] ENGINE Caught signal SIGTERM.
[08/Jan/2013:20:05:33] ENGINE Bus STOPPING
2013-01-08 20:05:33,920 : INFO : _cplogging:201 : error(CP Server Thread-3) : [08/Jan/2013:20:05:33] ENGINE Bus STOPPING
[08/Jan/2013:20:05:38] ENGINE Error in 'stop' listener <bound method Server.stop of <cherrypy._cpserver.Server object at 0x1090c3c90>>
Traceback (most recent call last):
File "/Volumes/work/workspace/vew/prj/lib/python2.7/site-packages/cherrypy/process/wspbus.py", line 197, in publish
output.append(listener(*args, **kwargs))
File "/Volumes/work/workspace/vew/prj/lib/python2.7/site-packages/cherrypy/process/servers.py", line 223, in stop
wait_for_free_port(*self.bind_addr)
File "/Volumes/work/workspace/vew/prj/lib/python2.7/site-packages/cherrypy/process/servers.py", line 410, in wait_for_free_port
raise IOError("Port %r not free on %r" % (port, host))
IOError: Port 8888 not free on '127.0.0.1'
我认为这发生在请求结束时,之后或期间pool.terminate()
。
分叉的工作进程不会对服务器或端口做任何事情。有没有办法告诉 CherryPy 和/或多处理忽略“服务器位”?我不需要任何端口或套接字fnc
。
我需要它在 OSX + Linux 上工作,使用 Python 2.7.1 和 CherryPy 3.2.2。
进展一:
根据 Sylvain 的建议,我尝试了pool = Pool(initializer=cherrypy.server.unsubscribe)
. 没有更多的例外,一切正常,但在日志中我看到
[08/Jan/2013:21:16:35] ENGINE Caught signal SIGTERM.
2013-01-08 21:16:35,908 : INFO : _cplogging:201 : error(CP Server Thread-10) : [08/Jan/2013:21:16:35] ENGINE Caught signal SIGTERM.
[08/Jan/2013:21:16:35] ENGINE Bus STOPPING
2013-01-08 21:16:35,909 : INFO : _cplogging:201 : error(CP Server Thread-10) : [08/Jan/2013:21:16:35] ENGINE Bus STOPPING
[08/Jan/2013:21:16:35] ENGINE Bus STOPPED
2013-01-08 21:16:35,909 : INFO : _cplogging:201 : error(CP Server Thread-10) : [08/Jan/2013:21:16:35] ENGINE Bus STOPPED
[08/Jan/2013:21:16:35] ENGINE Bus EXITING
2013-01-08 21:16:35,909 : INFO : _cplogging:201 : error(CP Server Thread-10) : [08/Jan/2013:21:16:35] ENGINE Bus EXITING
[08/Jan/2013:21:16:35] ENGINE Bus EXITED
2013-01-08 21:16:35,910 : INFO : _cplogging:201 : error(CP Server Thread-10) : [08/Jan/2013:21:16:35] ENGINE Bus EXITED
这样好吗?这会带来任何麻烦吗(例如,同时在不同线程中服务多个请求时)?
进展 2:
实际上上面偶尔会留下空闲进程:(所以它不能正常工作。奇怪的是,这些空闲进程是由 产生的Pool
,所以它们应该是守护进程,但即使在杀死父进程后它们实际上仍然活着。
进展 3:
我将分叉(=Pool()
调用)移到了请求处理方法之外,但是在初始化了所有必要的状态之后(以便工作进程可以看到这个状态)。没有更多的错误或异常。
底线:多处理和多线程不能一起工作。