Web应用的压力测试-loadrunner技术分析.ppt

系统性能调优 分析测试结果 运行场景 阶段 4 4.1 确认并发情况下Vuser正确运行 4.2 分离top time transactions 4.3 满载压力测试 4.4 Isolate hardware and software limitations 设计场景 阶段 3 3.1 配置测试主机 3.2 连接测试主机 3.3 配置脚本 3.4 添加虚拟用户 创建Web虚拟用户 阶段 2 2.1 录制用户操作 2.2 添加LoadRunner transactions 2.3 参数化 2.4 添加检查点 2.5 确认正确执行 LoadRunner 工作流程摘要 阶段 5 阶段 1 制定测试方案 1.1 获得系统使用信息 1.2 准备业务流程文档 1.3 确定参数化内容 1.4 准备测试数据 本章结束！谢谢！~ * * * * This is the process for a LoadRunner expert. In this course some steps will be presented in a different order to facilitate the learning process. * x * * * * * * The task distribution diagram displays the throughput of all business process relative to the timeline of a working day. By displaying this information in this format, peak times of usage can be isolated. * * The System Operation Profile diagram displays system usage in terms of the web system, rather than of the users. Besides business process, throughput and peak load times, the information can be expanded to include such things as: - Web server activity - DB interaction - Legacy system interaction - Level of risk should the business process malfunction You might have to rely on Functional experts, Project Managers and users to gather the information shown in this diagram. Usually, the users are inter-viewed about what business process they perform and how often they perform them. * * * * * * * * * Analysis and design. Patient and thorough modeling is necessary to accurately reflect the real-world user environment. Data refresh strategy. Should allow 3-4 test runs/day. Functional expertise. Availability of expert resources to LoadRunner team crucial to efficient design process. Debug/tune the system. Speedy design also requires availability of app/system admin experts. * Analysis and design. Patient and thorough modeling is necessary to accurately reflect the real-world user environment. Data refresh strategy. Should allow 3-4 test runs/day. Functional expertise. Availability of expert resources to LoadRunner team crucial to ef