␡
- Exercise 46: Alabama Cement
- Exercise 47: Alaska Tours and Such
- Exercise 48: Arizona Aluminum Manufacturing
- Exercise 49: Arkansas University
- Exercise 50: California Dreaming
- Exercise 51: Colorado Insurers
- Exercise 52: Connecticut Water
- Exercise 53: Delaware Trucking
- Exercise 54: Florida Reviewers
- Exercise 55: Georgia Widgets
- Exercise 56: Hawaii PineTrees, Inc.
- Exercise 57: Idaho Rock Quarries
- Exercise 58: Illinois Lotto
- Exercise 59: Indiana Reptiles
- Exercise 60: Iowa Retirement Homes
- Exercise 61: Kansas Vets, Ltd.
- Exercise 62: Kentucky’s D S Technical
- Exercise 63: Louisiana Fishing
- Exercise 64: Maine Asylums, LLC
- Exercise 65: Maryland Programming
- Exercise 66: Massachusetts Spammers
- Exercise 67: Michigan Growers
- Exercise 68: Minnesota River Authority
- Exercise 69: Mississippi Diabetes Group
- Exercise 70: Missouri Knife and Scissor
- Exercise 71: Montana Expeditions
- Exercise 72: North Carolina Swimmers
- Exercise 73: North Dakota Plastics
- Exercise 74: Nebraska Genealogy
- Exercise 75: Nevada Design
This chapter is from the book
Exercise 63: Louisiana Fishing
One of your clients, Louisiana Fishing, is worried that their network is receiving too much traffic, and responses for data are taking longer than they should. Although this is desirable in most businesses, Louisiana Fishing fears that they might not have the resources to keep up with an increase in their load.
Monitor the traffic on the SLES 9 server and look for any indication that traffic might be too heavy; then make an appropriate recommendation based on your findings.