Performance of the Firefly RPC Export

@article{citeulike:3403531, 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.}, address = {New York, NY, USA}, author = {Schroeder, Michael D. and Burrows, Michael}, citeulike-article-id = {3403531}, citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=77648.77653}, citeulike-linkout-1 = {http://dx.doi.org/10.1145/77648.77653}, doi = {10.1145/77648.77653}, issn = {0734-2071}, journal = {ACM Trans. Comput. Syst.}, keywords = {bulk-data-transport, inter-process-communication, lecture-aos, operating-system, remote-procedure-calls}, number = {1}, pages = {1--17}, posted-at = {2009-02-24 20:49:54}, priority = {0}, publisher = {ACM}, title = {Performance of the Firefly RPC}, url = {http://dx.doi.org/10.1145/77648.77653}, volume = {8}, year = {1990} }

TY - JOUR ID - citeulike:3403531 L3 - citeulike-article-id:3403531 N2 - 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. IS - 1 JF - ACM Trans. Comput. Syst. SN - 0734-2071 AD - New York, NY, USA EP - 17 TI - Performance of the Firefly RPC PB - ACM VL - 8 SP - 1 KW - bulk-data-transport KW - inter-process-communication KW - lecture-aos KW - operating-system KW - remote-procedure-calls AU - Schroeder, Michael AU - Burrows, Michael PY - 1990/// UR - http://dx.doi.org/10.1145/77648.77653 ER -