Xref: utzoo comp.protocols.misc:638 comp.sys.apollo:3175 comp.sys.hp:2552 comp.protocols.nfs:309
Path: utzoo!utgpu!jarvis.csri.toronto.edu!daemon
Newsgroups: comp.protocols.misc,comp.sys.apollo,comp.sys.hp,comp.protocols.nfs
From: cks@white.toronto.edu (Chris Siebenmann)
Subject: Re: A Comparison of Commerical RPC Protocols
Message-ID: <89Jul31.194335edt.30760@snow.white.toronto.edu>
Sender: <daemon>
Organization: Ziebmef home away from home
References: <6567@joshua.athertn.Atherton.COM> <951@anise.acc.com> <10258@boulder.Colorado.EDU> <44a7f591.1d6d5@apollo.COM>
Date: 31 Jul 89 23:43:57 GMT

mishkin@apollo.com (Nathaniel Mishkin) writes:
| I would imagine that the time to make a remote call is dominated (or
| at least significantly determined by) the networking costs (i.e. the
| cost of sending and receiving network messages).

 At least with Sun's RPC running over tcp, this is not the case as I
discovered to my surprise last summer. If you're exchanging structured
data, the networking overhead is completely swamped by XDR overhead,
even for Sun<->Sun connections using only integers.

-- 
	"I shall clasp my hands together and bow to the corners of the world."
			Number Ten Ox, "Bridge of Birds"
Chris Siebenmann		...!utgpu!{ncrcan,ontmoh!moore}!ziebmef!cks
cks@white.toronto.edu	     or ...!utgpu!{,csri!}cks