The Peregrine high-performance RPC system

DMCA

The Peregrine high-performance RPC system (1993)

Cached

Download Links

Other Repositories/Bibliography

DBLP

by David B. Johnson , Willy Zwaenepoel

Venue:	Software: Practice and Experience
Citations:	39 - 3 self

BibTeX

@ARTICLE{Johnson93theperegrine,
    author = {David B. Johnson and Willy Zwaenepoel},
    title = {The Peregrine high-performance RPC system},
    journal = {Software: Practice and Experience},
    year = {1993},
    volume = {23}
}

OpenURL

Abstract

The Peregrine RFT system provides performance very close to the optimum allowed by the hardware limits, while still supporting the complete RPC model. Implemented on an Ethernet network of Sun-3/60 workstations, a null RPC between two user-level threads executing on separate machines requires 573 ps. This time compares well with the fastest network RPC times reported in the literature, ranging from about 1100 to 2600 ps, and is only 309 ps above the measured hardware latency for transmitting the call and result packets in our environment. For large multi-packet RPC calls, the Peregrine user-level data transfer rate reaches 8.9 Mbit/s, approaching the Ethernet's 10 Mbit/s network transmission rate. Between two user-level threads on the same machine, a null RPC requires 149 ps. This paper identifies some of the key performance optimizations used in Peregrine, and quantitatively assesses their benefits. KEY WORDS Peregrine Remote procedure call Interprocess communication Performance Distributed sys-tems Operating systems

Keyphrases

peregrine high-performance rpc system null rpc user-level thread result packet network rpc time hardware limit mbit network transmission rate large multi-packet rpc separate machine peregrine user-level data transfer rate complete rpc model ethernet network hardware latency peregrine rft system key performance optimization

DMCA