A Software Architecture for Zero-Copy RPC in Java
| dc.contributor.author | Chang, Chi-Chao | en_US |
| dc.contributor.author | von Eicken, Thorsten | en_US |
| dc.date.accessioned | 2007-04-23T18:14:46Z | |
| dc.date.available | 2007-04-23T18:14:46Z | |
| dc.date.issued | 1998-10 | en_US |
| dc.description.abstract | RPC has established itself as one of the more powerful communication paradigms for distributed computing. In recent years, object-oriented languages have impacted RPC semantics, with a number of variants providing remote method invocation and various forms of distributed object systems. At the same time, performance has changed little with the bottleneck being the network transport, in particular the in-kernel protocol implementations. This paper describes J-RPC, an RPC architecture that leverages user-level network interfaces (UNI) to circumvent the kernel on the critical path. It describes how the wire format and the RPC system can be engineered to allow zero-copy reception of Java objects and zero-copy transmission of arrays. All objects received are fully type-checked and can be directly used by the receiving program. The design is connection-oriented for performance and leverages the JVM's garbage collector when managing receive buffers. An implementation built from an off-the-shelf JVM and a commercial UNI is used to evaluate the architecture and the tradeoffs of type-safe, zero-copy data marshaling. | en_US |
| dc.format.extent | 354016 bytes | |
| dc.format.extent | 1291153 bytes | |
| dc.format.mimetype | application/pdf | |
| dc.format.mimetype | application/postscript | |
| dc.identifier.citation | http://techreports.library.cornell.edu:8081/Dienst/UI/1.0/Display/cul.cs/TR98-1708 | en_US |
| dc.identifier.uri | https://hdl.handle.net/1813/7362 | |
| dc.language.iso | en_US | en_US |
| dc.publisher | Cornell University | en_US |
| dc.subject | computer science | en_US |
| dc.subject | technical report | en_US |
| dc.title | A Software Architecture for Zero-Copy RPC in Java | en_US |
| dc.type | technical report | en_US |