Path: utzoo!mnetor!uunet!husc6!rutgers!ames!ucbcad!ucbvax!SRI-ROBOTX.ARPA!HERSON
From: HERSON@SRI-ROBOTX.ARPA (Jim Herson)
Newsgroups: comp.os.vms
Subject: DECNet's task to task speed
Message-ID: <566072617.0.HERSON@SRI-ROBOTX.ARPA>
Date: 9 Dec 87 18:23:37 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 35



We are using DECNet for simple task to task communications and
are very disappointed in throughput. We are wondering if we
have implemented something incorrectly.  Our benchmarks are as
follows:

        time per    | machine running | machine running
        packet(ms)  | process A       | process B
        ---------------------------------------------
        4.0         | 8600	      | 8600
        ---------------------------------------------
        28.3        | 8600	      | 730
        ---------------------------------------------
        34.7        | 730	      | 730


These times are based on an average of 1000 packets, each 500 bytes long.
3/4 of the total time is spent in the network and 1/4 in our code. All
tests were run on unloaded machines (each with plenty of memory).  The
basic loop is:
	1. issue a read request
	2. hibernate until the read completes and the AST is invoked.
	3. do some minor bookkeeping and turn the packet around.


Any pointers or information on similar experiences would be appreciated.

Thank you


Jim Herson
(HERSON@ROBOTX.SRI.COM)

-------