distributed computing implementations

[Irmen de Jong]

Duncan Grisby wrote:

> Interesting article. Unfortunately, the first two timings of the CORBA
> client aren't timing what Mike thinks they are. The first time, for
> "connecting to server" doesn't actually connect to the server at all.
> It just creates an object reference for it.
> 
> The second time, for "send string" _is_ timing sending a string, but
> that is also when the TCP connection to the server is made. A
> significant portion of the time is spent setting up the connection,
> not transferring the string. If I modify the client to do the first
> call twice, I get
> 
> Connecting to server
> Time to connect to server, 0.000386
> 
> Sending a long string to the server
> Time to send a string of 21000 chars, 0.002099
> 
> Sending a long string to the server
> Time to send a string of 21000 chars, 0.001034
> 
> Recieving a long stirng from the server
> Time to receive a string of 22000 chars, 0.001088
> 
> Sending lots of ints to the server
> Time to send 5000 ints, 0.921309 (0.000184 per call)
> 


To add some more to the mix, I benchmarked Pyro (3.2) :

Connecting to server
Time to connect to server, 0.026004

Sending a long string to the server
Time to send a string of 21000 chars, 0.003536

Recieving a long stirng from the server
Time to receive a string of 22000 chars, 0.003387

Sending lots of ints to the server
Time to send 5000 ints, 10.057741 (0.002012 per call)

I find this very fast for a pure Python solution....

I also measured the message sizes with tcpdump as mentioned in the article:

Actual message size sending 1,000 characters: 1390
Actual message size sending 100 integers: 27698 (with CORBA amongst the 
smallest)


> Lies, damn lies, and statistics...

Amen.

--Irmen de Jong