Difference between revisions of "MultiProcessCompute"
m (Text replace - "__NOTOC__" to "") |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | ||
All services in Nova currently use eventlet as it's basis for concurrency. Experience with eventlet has resulted in a handful of downsides: | All services in Nova currently use eventlet as it's basis for concurrency. Experience with eventlet has resulted in a handful of downsides: | ||
Latest revision as of 23:29, 17 February 2013
All services in Nova currently use eventlet as it's basis for concurrency. Experience with eventlet has resulted in a handful of downsides:
- Integration with Python and third-party libraries is less than perfect
- It is a source of some hard-to-troubleshoot bugs in logging and exception handlers
Experience with running the compute service has shown that there is little shared state between threads. As a result, switching to a multi-process model should help avoid the downsides of eventlet, while providing an well understood and easy to use model.
