QuoteRef: vanrR10_1988

topics > all references > ThesaHelp: references t-z

references t-z
ACM references m-z
examples of distributed systems and applications
a single system image
object-oriented programming
abstract data type
client-server model for distributed systems
object-oriented data types
remote procedure call
object-oriented objects
security by capabilities
communication protocols
software portability
information as a hint
locating named objects by broadcast
unique numeric names as surrogates
communication port
disk allocation
immutable files and data
memory management by garbage collection
file system reliability
replicated data
examples of file systems
asynchronous processing


van Renesse, R., van Staveren, H., Tanenbaum, A.S., "Performance of the world's fastest distributed operating system", Operating Systems Review, 22, 4, pp. 25-34, ACM, October 1988. Google

26 ;;Quote: Amoeba consists of workstations, pool processors for dynamic allocation, specialized servers, and wide-area network gateways
26+;;Quote: using wide-area network gateways, Amoeba forms a single, uniform system across possibly different countries
26 ;;Quote: Amoeba is an object-oriented distributed operating system
26+;;Quote: Amoeba objects are abstract data types managed by server processes
26+;;Quote: Amoeba servers accessed by remote procedure call (called "transactions")
26 ;;Quote: all Amoeba objects are named and cryptographically protected by capabilities; e.g., access a file by a capability
27 ;;Quote: Amoeba messages consist of a 32 byte header and up to a 30K byte buffer; will be 64 bytes and 1 gigabyte respectively
27+;;Quote: Amoeba request headers with capability for object, operation code, 8 bytes for parameters
27+;;Quote: Amoeba reply headers with error code, 8 bytes of result, and a returned capability
26 ;;Quote: Amoeba remote procedure calls are executed at-most-once; returns success, not executed, or unknown (lost contact, caller must recover)
27 ;;Quote: Amoeba implements remote procedure calls on each processor and in UNIX; allows transparent use of Amoeba
27+;;Quote: small transactions (remote procedure calls) need a short delay while large ones need a high bandwidth
28 ;;Quote: the first DO-TRANSACTION broadcasts the server's port to find its physical network address; used for future transactions (a hint)
28+;;Quote: Amoeba uses server ports (48 bits) to identify a server independently of its network address
28 ;;Quote: the reply message for an Amoeba transaction also acknowledges the request; if delayed, the request is retransmitted and acknowledged
28 ;;Quote: efficient implementation of remote procedure calls by fast code, sweep algorithm for time-outs, and fast context switching
28+;;Quote: Amoeba uses a sweep algorithm to implement time-outs for its communication protocols; periodically checks for progress
30 ;;Quote: Amoeba's RPC delay is 10 times faster than UNIX for short messages and 3 times higher bandwidth for large ones; none better
30 ;;Quote: Amoeba's bullet server stores files contiguously, both on the disk and in the server's main memory; for rapid access
31 ;;Quote: Amoeba's bullet server stores immutable files with read, create, and delete operations; transferred as a unit
31+;;Quote: Amoeba's bullet server deletes old versions when not in the file directory of name, capability pairs; garbage collection
31 ;;Quote: Amoeba files are replicated on two disks; the create-file operation can return when 0, 1 or 2 copies written to disk
31 ;;Quote: a file's capability includes its i-node index; Amoeba's memory-resident i- node table gives the disk and cache address; at most 1 disk seek
31 ;;Quote: Amoeba's create-file operation generates a capability; generating and encrypting the random number is costly (120 msec)
31 ;;Quote: Amoeba's bullet file server reads 2-3 times faster than SUN NFS; large write bandwidth is 4 times higher; small file create is slower

Related Topics up

ThesaHelp: references t-z (309 items)
ThesaHelp: ACM references m-z (280 items)
Topic: examples of distributed systems and applications (24 items)
Topic: a single system image (30 items)
Group: object-oriented programming   (26 topics, 814 quotes)
Topic: abstract data type (64 items)
Topic: client-server model for distributed systems (25 items)
Topic: object-oriented data types (29 items)
Topic: remote procedure call (44 items)
Topic: object-oriented objects (36 items)
Topic: security by capabilities (65 items)
Topic: communication protocols (61 items)
Topic: software portability (43 items)
Topic: information as a hint (18 items)
Topic: locating named objects by broadcast (9 items)
Topic: unique numeric names as surrogates (67 items)
Topic: communication port (40 items)
Topic: disk allocation (32 items)
Topic: immutable files and data (57 items)
Topic: memory management by garbage collection (113 items)
Topic: file system reliability (26 items)
Topic: replicated data (45 items)
Topic: examples of file systems (44 items)
Topic: asynchronous processing (30 items)

Collected barberCB 9/90
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.