ACM Home Page
Please provide us with feedback. Feedback
Performance of the Firefly RPC
Full text PdfPdf (1.35 MB)
Source ACM Transactions on Computer Systems (TOCS) archive
Volume 8 ,  Issue 1  (February 1990) table of contents
Pages: 1 - 17  
Year of Publication: 1990
ISSN:0734-2071
Authors
Michael D. Schroeder  Digital Equipment Corp., Palo Alto, CA
Michael Burrows  Digital Equipment Corp., Palo Alto, CA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 40,   Citation Count: 40
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/77648.77653
What is a DOI?

ABSTRACT

In this paper we report on the performance of the remote procedure call (RPC) implementation for the Firefly multiprocessor and analyze the implementation to account precisely for all measured latency. From the analysis and measurements, we estimate how much faster RPC could be if certain improvements were made. The elapsed time for an intermachine call to a remote procedure that accepts no arguments and produces no results is 2.66 ms. The elapsed time for an RPC that has a single 1440-byte result (the maximum result that will fit in a single packet) is 6.35 ms. Maximum intermachine throughput of application program data using RPC is 4.65 Mbits/s, achieved with four threads making parallel RPCs that return the maximum-size result that fits in a single RPC result packet. CPU utilization at maximum throughput is about 1.2 CPU seconds per second on the calling machine and a little less on the server. These measurements are for RPCs from user space on one machine to user space on another, using the installed system and a 10 Mbit/s Ethernet. The RPC packet exchange protocol is built on IP/UDP, and the times include calculating and verifying UDP checksums. The Fireflies used in the tests had 5 MicroVAX II processors and a DEQNA Ethernet controller.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
2
3
 
4
DIGITAL EQUIPMENT CORP. Microsystems Handbook. Digital Equipment Corp., Palo Alto, Calif., 1985 Appendix A.
 
5
DIGITAL EQUIPMENT CORP. DEQNA ETHERNETmUser's Guide. Digital Equipment Corp., Palo Alto, Calif., Sept. 1986.
 
6
 
7
ROVNER, P.R. Extending Modula-2 to build large, integrated systems. IEEE Softw. 37, 8 (Nov. 1986), 46-57.
 
8
9

CITED BY  40


REVIEW

"Andrew S. Tanenbaum : Reviewer"

Most computer science research papers in the systems area focus on the design and sometimes the implementation of the system in question. Rarely is the performance of the resulting system measured (assuming the system is actually built), and m  more...

Collaborative Colleagues:
Michael D. Schroeder: colleagues
Michael Burrows: colleagues