Access the full text.
Sign up today, get DeepDyve free for 14 days.
Monitoring System Performance. This is the final installment of a multipart article on resource usage issues in library automation systems. The first three parts dealt with specifying resource usage and performance goals. This article will deal with monitoring system performance. Most system monitoring in the current library automation world is anecdotal. The person responsible for the system receives a telephone call, or many calls, indicating that the system is not performing properly. Usually, that is the sum total statement of performance. By the time an individual actually becomes frustrated enough to call about the system's degraded performance, their perception of the problem has generally grown far worse that the problem actually is. Yet, in many cases, the perception is what really matters and it is often quite impossible to budge people from that perception once it is formed.
Academic and Library Computing – Emerald Publishing
Published: Apr 1, 1991
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.