晀栗楮汥敍虑-CapacityPlanninginClientServer.ppt

Capacity Planning in Client/Server Environments Daniel A. Menascé George Mason University Fairfax, VA 22030 USA menasce@ Outline Part I: Client/Server Systems Part II: Introduction to Capacity Planning Part III: A Capacity Planning Methodology for C/S Environments Part IV: Performance Prediction Models for C/S Environments Outline (continued) Part V: Advanced Predictive Models of C/S Systems Part VI: Case Study Bibliography Part I:Client/Server (C/S) Systems Definitions and Basic Concepts Client Server Work division between client and server Client/Server communication Definitions and basic concepts Definitions and basic concepts:Client Workstation with graphics and processing capabilities. Graphical User Interface (GUI) implemented at the client. Partial processing executed at the client. Definitions and basic concepts:Server Machine with much larger processing and I/O capacity than the client. Serves the various requests from the clients. Executes a significant portion of the processing and I/O of the requests generated at the client. Work division between client and server Interaction between client and serverRemote Procedure Call (RPC) Part II:Introduction to Capacity Planning Migration to C/S example:“downsizing” a claim processing application DB server connected to several PCs through an Ethernet LAN GUI application executing at the PCs LAN connected to the enterprise mainframe through a T1 line DB server is updated every night. Migration to C/S systems mainframe based system Migration to C/S DB server based system Migration to C/S:some important questions How many clients can be supported by the DB server while maintaining a response time below 2.5 sec? How long does it take to update the DB every night? Migration to C/S example: measurements with a prototype During 30 minutes (1,800 sec): 25% CPU utilization 30% disk utilization 800 transactions were executed Each transaction used: 1,800 * 0.25 / 800 = 0.56 sec of CPU and 1,800 * 0.30