ACM Home Page
Please provide us with feedback. Feedback
Manageability, availability and performance in Porcupine: a highly scalable, cluster-based mail service
Full text pdf formatPdf (1.62 MB)
Source ACM Symposium on Operating Systems Principles archive
Proceedings of the seventeenth ACM symposium on Operating systems principles table of contents
Charleston, South Carolina, United States
Pages: 1 - 15  
Year of Publication: 1999
ISBN:1-58113-140-2
Also published in ...
Authors
Yasushi Saito  Department of Computer Science and Engineering, University of Washington
Brian N. Bershad  Department of Computer Science and Engineering, University of Washington
Henry M. Levy  Department of Computer Science and Engineering, University of Washington
Sponsor
SIGOPS: ACM Special Interest Group on Operating Systems
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 34,   Citation Count: 34
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/319151.319152
What is a DOI?

ABSTRACT

This paper describes the motivation, design, and performance of Porcupine, a scalable mail server. The goal of Porcupine is to provide a highly available and scalable electronic mail service using a large cluster of commodity PCs. We designed Porcupine to be easy to manage by emphasizing dynamic load balancing, automatic configuration, and graceful degradation in the presence of failures. Key to the system's manageability, availability, and performance is that sessions, data, and underlying services are distributed homogeneously and dynamically across nodes in a cluster.


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
Andrew D. Birrell, Andy Hisgen, Chuck Jerian, Timothy Mann, and Garret Swart. The Echo distributed file system. Technical Report 111, Compaq Systems Research Center, Palo Alto, CA, September 1993.
 
3
Thomas P. Brisco. RFC1794: DNS support for load balancing, April 1995. http://www, cis.ohiostate.edu/htbin/rfc/rfc 1794.html.
 
4
Nick Christenson, Tim Bosserman, and David Beckemeyer. A highly scalable electronic mail service using open systems. In USENIX Symposium on Internet Technologies and Systems, Monterey, CA, December 1997.
 
5
Flaviu Christian and Frank Schmuck. Agreeing on processor group membership in asynchronous distributed systems. Technical Report CSE95-428, UC San Diego, 1995.
 
6
Cisco Systems. Local director, http://www, cisco.com/- warp/public/751/lodir/index.html.
 
7
Marc Crispin. RFC2060: Internet message access protocol version 4 rev 1, December 1996. http ://www. cis.ohio- state.edu/htbin/rfc/rfc2060.html.
 
8
 
9
James Deroest. Clusters help allocate computing resources, http://www'washingt~n'edu/tech-h~me/- windows/issue 18/clusters.html, 1996.
 
10
11
 
12
13
14
15
16
 
17
David L. Mills. RFC1305: Network time protocol (version 3), March 1992. http://www, cis.ohiostate, edu/htbin/rfc/rfc 1305.html.
18
 
19
Michael Mitzenmacher. How useful is old information? Technical Report 98-002, Compaq Systems Research Center, Palo Alto, CA, February 1998.
 
20
John G. Myers and Marshall T. Rose. RFC1939: Post office protocol version 3, May 1996. http://www, cis.ohio-state.edu/htbin/rfc/rfc1939.html.
21
 
22
Jonathan Postel. RFC821: Simple mail transfer protocol, August 1982.http://www, cis.ohiostate, edu/htbin/rfc/rfc 821 .html.
23
24
 
25
Theodore Ts'o. Ext2 home page, 1999. http://web.- mit.edu/tytso/www/linux/ext2.html.
 
26
27

CITED BY  34
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Collaborative Colleagues:
Yasushi Saito: colleagues
Brian N. Bershad: colleagues
Henry M. Levy: colleagues

Peer to Peer - Readers of this Article have also read: