[PythonCE] very slow XMLRPCServer

Warren Lindsey warren.lindsey at gmail.com
Mon May 18 23:17:31 CEST 2009

Sounds like this might be dns related.  If the server is doing reverse
lookups (and subsequent timeouts) for every incoming connection it can
be quite slow.  You might want to add local entries the registry on
the ipaq for hostname lookups.  Windows mobile/ce doesn't have an
/etc/hosts file, but it does support an equiv feature in the registry.

There was a tool I used to have and I thought it was call ceHosts to
update entries, but I'm not finding it in a quick google search.  I
did however find a link to a tip on updating the registry directly


Obviously, the same should be done on the server to ensure ip lookups
on your ipaq device are fast as well.  Even if you're connecting by ip
address, the client or server in a tcpip environment may do a reverse
lookup on connections.


On Mon, May 18, 2009 at 2:06 PM, Thomas Heller <theller at ctypes.org> wrote:
> David McNab schrieb:
>> Hi,
>> I'm trying to run an XML-RPC server on my ipaq h4100, based on the
>> python 'SimpleXMLRPCServer', but it's ridiculously slow to process
>> requests.
>> Turnaround for even the simplest client requests is around 30-40
>> seconds.
> I don't know if this will help you or not:
> I tried to use XMLRPC betweem a small embedded ARM system runing linux
> and a Windows PC.  The performance of a client on the PC and a server on
> the embedded system was acceptable (~10 requests per second), but the
> server on the PC called by a client running on the embedded system was unacceptable:
> 1 request took around 5 seconds to complete.
> I have since switched to jsonrpc instead of xmlrpc which has a
> much better performance: around 70 requests per second, in both
> directions.
> Thomas
> _______________________________________________
> PythonCE mailing list
> PythonCE at python.org
> http://mail.python.org/mailman/listinfo/pythonce

More information about the PythonCE mailing list