On 08:21 pm, [email protected] wrote: >I've got some CPU scalability issues (the application became CPU bound, >but there are a lot more CPUs, which can't be used because of the >uniprocess nature), threading is not a solution, so the next logical >move could be starting multiple twisted reactors in different processes >and transparently switching incoming connections between them. >There is no need for intra-process communication, I need only a thing, >which does the process starting/stopping, connection multiplexing in a >clean way.
Have you looked at Ampoule? https://launchpad.net/ampoule/ _______________________________________________ Twisted-Python mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
