There is another Python based XMLRPC library available on sourceforge, also linked on xmlrpc.com. This library is written in C and the author says that it is some magnitude faster than xmlrpclib. The catch? It won't work with zope without some manipulation, cos the author hardcoded the case on the HTTP headers, afaik this is not strictly kosher as the headers can be any case (UPPER, lower or Mixed). Might be worth a look though. Phil ----- Original Message ----- From: "Toby Dickenson" <tdickenson@devmail.geminidataloggers.co.uk> To: <magnus/Websys@websys.no> Cc: <zope@zope.org> Sent: Friday, May 11, 2001 4:40 PM Subject: Re: [Zope] xmlrpc slowness
On Fri, 11 May 2001 17:06:52 +0200, magnus/Websys@websys.no wrote:
We're busy developing an application that uses Zope for its presentation layer. To communicate with the 'business logic' Java layer, we use xml-rpc with Zope as the client.
How much data are you marshalling?
It works fine, but seems to be slightly slow. Each and every xml-rpc transaction takes appx. 3/10 of a second. I have installed sgmlop, and that improved matters (from 7/10 of a second) - can anyone suggest how to make further improvements?
Ive been using xmlrpc with parameters and return values that involve lists with 1000's of elements - 300ms is not unreasonable. If you are marshalling smaller things then it should be faster.
I haven't done any real testing,
Do some. Zope's profiler should give you the answers you need.
Toby Dickenson tdickenson@geminidataloggers.com
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )