Relation de la Mission Abnaquise de St. Franðcois de Sales L'Annâee 1702 / par le Páere Jacques Bigot, de la Compagnie de Jâesus.

http://www.archive.org/details/missionabnaquise00bigorich

Indian missions on the north Pacific coast.

http://www.archive.org/details/indianmissionson00tororich

James Evans : inventor of the syllabic system of the Cree language / by John McLean ... (Robin Rustler).

http://www.archive.org/details/jamesevans00maclrich

Las órdenes religiosas de España y la colonización de América en la segunda parte del siglo XVIII : estadístacas y otros documentos

http://www.archive.org/details/bordenesreligiosas01maasrich/

Mary and I. Forty years with the Sioux.

http://www.archive.org/details/maryandifortyyea00riggrich

Catholic grievances in relation to the administration of Indian affairs : being a report presented to the Catholic Young Men's National Union, at its eighth annual convention, held in Boston, Massachusetts, May 10th and 11th, 1882

http://www.archive.org/details/catholicgrieva00mealrich

First ten annual reports of the American Board of Commissioners for Foreign Missions : with other documents of the Board.

http://www.archive.org/details/firsttenannualre00amerrich

History of Baptist Indian missions : embracing remarks on the former and present condition of the aboriginal tribes; their settlement within the Indian Territory, and their future prospects / by Isaac McCoy.

http://www.archive.org/details/baptistindianmiss00mccorich

The Missionary pioneer, or, A brief memoir of the life, labours, and death of John Stewart, (man of colour) founder, under God of the mission among the Wyandotts at Upper Sandusky, Ohio / Published by Joseph Mitchell.

http://www.archive.org/details/missionarypionee00stewrich

Stranger than fiction. [electronic resource] By the Rev. J.J. Halcombe

http://digilib.bu.edu/archive/strangerthanfict00halcrich/strangerthanfict00halcrich.djvu

Measuring the Behavior of a World-Wide Web Server

Server performance has become a crucial issue for improving the overall performance of the World-Wide Web. This paper describes Webmonitor, a tool for evaluating and understanding server performance, and presents new results for a realistic workload. Webmonitor measures activity and resource consumption, both within the kernel and in HTTP processes running in user space. Webmonitor is implemented using an efficient combination of sampling and event-driven techniques that exhibit low overhead. Our initial implementation is for the Apache World-Wide Web server running on the Linux operating system. We demonstrate the utility of Webmonitor by measuring and understanding the performance of a Pentium-based PC acting as a dedicated WWW server. Our workload uses a file size distribution with a heavy tail. This captures the fact that Web servers must concurrently handle some requests for large audio and video files, and a large number of requests for small documents, containing text or images. Our results show that in a Web server saturated by client requests, over 90% of the time spent handling HTTP requests is spent in the kernel. Furthermore, keeping TCP connections open, as required by TCP, causes a factor of 2-9 increase in the elapsed time required to service an HTTP request. Data gathered from Webmonitor provide insight into the causes of this performance penalty. Specifically, we observe a significant increase in resource consumption along three dimensions: the number of HTTP processes running at the same time, CPU utilization, and memory utilization. These results emphasize the important role of operating system and network protocol implementation in determining Web server performance.

On the Interaction Between an Operating System and Web Server

This paper examines how and why web server performance changes as the workload at the server varies. We measure the performance of a PC acting as a standalone web server, running Apache on top of Linux. We use two important tools to understand what aspects of software architecture and implementation determine performance at the server. The first is a tool that we developed, called WebMonitor, which measures activity and resource consumption, both in the operating system and in the web server. The second is the kernel profiling facility distributed as part of Linux. We vary the workload at the server along two important dimensions: the number of clients concurrently accessing the server, and the size of the documents stored on the server. Our results quantify and show how more clients and larger files stress the web server and operating system in different and surprising ways. Our results also show the importance of fixed costs (i.e., opening and closing TCP connections, and updating the server log) in determining web server performance.

Connection Scheduling in Web Servers

Under high loads, a Web server may be servicing many hundreds of connections concurrently. In traditional Web servers, the question of the order in which concurrent connections are serviced has been left to the operating system. In this paper we ask whether servers might provide better service by using non-traditional service ordering. In particular, for the case when a Web server is serving static files, we examine the costs and benefits of a policy that gives preferential service to short connections. We start by assessing the scheduling behavior of a commonly used server (Apache running on Linux) with respect to connection size and show that it does not appear to provide preferential service to short connections. We then examine the potential performance improvements of a policy that does favor short connections (shortest-connection-first). We show that mean response time can be improved by factors of four or five under shortest-connection-first, as compared to an (Apache-like) size-independent policy. Finally we assess the costs of shortest-connection-first scheduling in terms of unfairness (i.e., the degree to which long connections suffer). We show that under shortest-connection-first scheduling, long connections pay very little penalty. This surprising result can be understood as a consequence of heavy-tailed Web server workloads, in which most connections are small, but most server load is due to the few large connections. We support this explanation using analysis.