These results are from preliminary tests.
Configuration
One GigaNet,Inc ATM board installed in rogue.css.ornl.gov, a 4-node (MP3/NIC B), 128 MB/node, (can run either NIC A or NIC B kernel and one service node Paragon. OSF 1.3.0. New libatm.a (10/23/95) Second ATM board in Intel's XPE (mpdot1.ccs.ornl.gov), 16-node GP/NIC A, same software.
Sandia has provided a FORE ATM switch with OC12 and OC3 interfaces, a BBN long link emulator, and an AT&T EMMI .
Compute node atm message-passing tests
Tom Dunigan ran a number of message passing tests using a compute node on each Paragon communicating through ATM. We booted rogue with a NIC A kernel to better emulate the SC 95 configuration. We ran echo tests, sink tests, and exchange tests to characterize message transfer time and bandwidth as a function of message size. (Click here for description of tests and see the test results from 10/19.)
Slightly slower throughput and higher jitter was observed when using a service node on each Paragon. On 11/3/95, we did see some full duplex performance, two concurrent and opposing sink tests achieved an aggregate date rate of 82 MB/s.
Here is a summary of compute-node communications, including using two Paragons (NIC A).
PVM/ATM tests
Phil Papadopoulus has worked on porting, testing, and tuning PVM for the ATM API.
ATM OC3 delay tests
Tom Pratt and Alden Jackson have designed a series of tests (see test configurations ). Here are results from 10/31/95 tests using two NIC A Paragons and the echo test. Time is 1-way time to transmit a 4-byte message, and bandwidth is measured with a 60KB message. The delay is only in one direction. Tests from OC12 into OC3 would hang for messages larger than 8 KB. We believe these failures are caused by the FORE switch (version 3.4.2).
IP/ATM and ATM video tests
The test configuration for IP over ATM and ATM video is depicted here.