RMI Netwoek Overhead

Mon May 19 07:50:00 GMT 2003

> We are making a master thesis and in that we are comparing overhead sizes on 
> method calls
> using RMI,RMI-IIOP, CORBA, DCOM and .Net Remoting. 

Interesting.
We're using Apache XmlRpc. Such a pity that you didn't include it. We
would love to see it compared to other remote method calling
technologies.
Another variable to compare, could be the size of libraries needed to
implement remote method calls. The full liborg-apache-xmlrpc-1-1.a
compiles to an unstripped 253.4 KB. That's all you need to add to your
executable to allow it to operate in a distributed method concert.
I wonder what the minimum footprint requirements are of a .Net
executable? I guess you could start by dragging around their 20 Mb
runtime download and deploy it to all users (don't forget to send
someone over to click "Ok" everywhere); and the footprint would be
inflated from there. How much wasted bandwith does that actually
represent on your network? That could pay for quite a bit of overhead in
the method calls ...