On Fri, Jan 6, 2012 at 3:02 PM, Balachandran Sivakumar <benignb...@gmail.com > wrote:
> Hi, > > On Fri, Jan 6, 2012 at 2:29 PM, Senthil <skksun...@yahoo.co.in> wrote: > > Hi All, > > > > I have an xmlRPC standalone server written wholly in python. Now am > facing problems in scaling the services. The more we start adding features, > the response gets slower. Is there any alternate server architectures i > should start thinking of ? This server works on basis of threaded > architecture and am seeing some complaints about threading in python. > Should i be considering anything else ? > We had a very simillar problem in our project https://github.com/FOSSEE/online_test We circumvent the xmlRPC 2 concurrent sessions problem by making a server pool. You can check the xmlRPC server pool code in this file https://github.com/FOSSEE/online_test/blob/master/testapp/code_server.py > > It depends on the implementation aspects. I am not very sure > about threads, but for these scenarios, we should ideally be using > reactor/proactor patterns. IIRC, all twisted[1] implementations are > reactors. So, you can switch to twisted. Still proactors are even > better. If you could implement one with Proactors, that should be even > more efficient and scalable. Thanks > > [1] Twisted XML-RPC: > http://twistedmatrix.com/documents/current/web/howto/xmlrpc.html > > -- > Thank you > Balachandran Sivakumar > > Arise Awake and stop not till the goal is reached. > - Swami > Vivekananda > > Mail: benignb...@gmail.com > Blog: http://benignbala.wordpress.com/ > _______________________________________________ > BangPypers mailing list > BangPypers@python.org > http://mail.python.org/mailman/listinfo/bangpypers > -- Regards Parth Buch *http://parthbuch.in* _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
