Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group 2002-06-24 - 2002-06-26.

Slides:



Advertisements
Similar presentations
Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group
Advertisements

Cultural Heritage in REGional NETworks REGNET Report on Content Group Meeting Extended Project Management Group Meeting
Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group Part 3: Content Testing.
Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group Part 1: Usability Testing.
Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group
Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group Part 2: Functional Testing.
Cultural Heritage in REGional NETworks REGNET PCM.
Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group
Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group
High level QA strategy for SQL Server enforcer
QA practitioners viewpoint
Topics to be discussed Introduction Performance Factors Methodology Test Process Tools Conclusion Abu Bakr Siddiq.
Performance Testing - Kanwalpreet Singh.
Web Performance Tuning Lin Wang, Ph.D. US Department of Education Copyright [Lin Wang] [2004]. This work is the intellectual property of the author. Permission.
Executional Architecture
SSRS 2008 Architecture Improvements Scale-out SSRS 2008 Report Engine Scalability Improvements.
Network Design and Implementation
Network Redesign and Palette 2.0. The Mission of GCIS* Provide all of our users optimal access to GCC’s technology resources. *(GCC Information Services:
Web Server Hardware and Software
Scaling Service Requests Linux: ipvsadm & iptoip.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 8: Implementing and Managing Printers.
MCITP Guide to Microsoft Windows Server 2008 Server Administration (Exam #70-646) Chapter 14 Server and Network Monitoring.
Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.
Module 8: Monitoring SQL Server for Performance. Overview Why to Monitor SQL Server Performance Monitoring and Tuning Tools for Monitoring SQL Server.
1 CSE 403 Reliability Testing These lecture slides are copyright (C) Marty Stepp, They may not be rehosted, sold, or modified without expressed permission.
Hands-On Microsoft Windows Server 2008 Chapter 11 Server and Network Monitoring.
MSF Testing Introduction Functional Testing Performance Testing.
1 © Mahindra Satyam 2009 Performance Testing as a Service using jMeter.
Load Test Planning Especially with HP LoadRunner >>>>>>>>>>>>>>>>>>>>>>
Virtual Memory Tuning   You can improve a server’s performance by optimizing the way the paging file is used   You may want to size the paging file.
Windows Server MIS 424 Professor Sandvig. Overview Role of servers Performance Requirements Server Hardware Software Windows Server IIS.
Types of Operating System
Chapter-4 Windows 2000 Professional Win2K Professional provides a very usable interface and was designed for use in the desktop PC. Microsoft server system.
Introduction to HP LoadRunner Getting Familiar with LoadRunner >>>>>>>>>>>>>>>>>>>>>>
TESTING STRATEGY Requires a focus because there are many possible test areas and different types of testing available for each one of those areas. Because.
Module 13: Configuring Availability of Network Resources and Content.
Software Testing Life Cycle
1 Guide to Novell NetWare 6.0 Network Administration Chapter 13.
Windows 2000 Advanced Server and Clustering Prepared by: Tetsu Nagayama Russ Smith Dale Pena.
5 Chapter Five Web Servers. 5 Chapter Objectives Learn about the Microsoft Personal Web Server Software Learn how to improve Web site performance Learn.
XA R7.8 Link Manager Belinda Daub Sr. Technical Consultant 1.
Module 9 Planning a Disaster Recovery Solution. Module Overview Planning for Disaster Mitigation Planning Exchange Server Backup Planning Exchange Server.
1 Week #10Business Continuity Backing Up Data Configuring Shadow Copies Providing Server and Service Availability.
Apache JMeter By Lamiya Qasim. Apache JMeter Tool for load test functional behavior and measure performance. Questions: Does JMeter offers support for.
Network design Topic 6 Testing and documentation.
Module 9 Planning and Implementing Monitoring and Maintenance.
Performance Testing Test Complete. Performance testing and its sub categories Performance testing is performed, to determine how fast some aspect of a.
1 Copyright © 2005, Oracle. All rights reserved. Following a Tuning Methodology.
SPI NIGHTLIES Alex Hodgkins. SPI nightlies  Build and test various software projects each night  Provide a nightlies summary page that displays all.
Understanding Performance Testing Basics by Adnan Khan.
The Planning Phase Recognize the problem MIS steering committee 7. ManagerSystems analyst Define the problem Set system objectives Identify system constraints.
Introduction to Performance Testing Performance testing is the process of determining the speed or effectiveness of a computer, network, software program.
1 Chapter Overview Monitoring Access to Shared Folders Creating and Sharing Local and Remote Folders Monitoring Network Users Using Offline Folders and.
LOAD RUNNER. Product Training Load Runner 3 Examples of LoadRunner Performance Monitors Internet/Intranet Database server App servers Web servers Clients.
Proctor Caching and System Check September 4, 2014 Becky Hoeft Conference Number: (877) Conference Pin:
Technology Coordinator Training. Agenda Getting Started Using SystemCheck Technology Configurations Infrastructure Trial Proctor Caching Overview Managing.
Intro to Web Server Load Testing © Thank you for attending Introduction to Web Server Load Testing.
1 Presented by: Val Pennell, Test Tool Manager Date: March 9, 2004 Software Testing Tools – Load Testing.
Session on Load Testing - Alok Agarwal. Agenda for the session Definitions Example on load testing What to Avoid When Testing for Load Goals of Load Testing.
Cofax Scalability Document Version Scaling Cofax in General The scalability of Cofax is directly related to the system software, hardware and network.
1 DEPLOYMENT AND OPERATIONS MODULE 23 ECM SPECIALIST COURSE 1 Copyright AIIM.
SQL Database Management
Software Architecture in Practice
Types of Operating System
Network Load Balancing
Top-Down Network Design Chapter Twelve Testing Your Network Design
Migration Strategies – Business Desktop Deployment (BDD) Overview
Moodle Scalability What is Scalability?
Specialized Cloud Architectures
Presentation transcript:

Cultural Heritage in REGional NETworks REGNET Project Meeting Content Group

June 2002REGNET Project Team Meeting Content Group 2 Why load tests and stress tests Complex systems make increasing demands on web servers Multiple objects can interfere High volumes can overwhelm systems Fixes need to be identified To identify bottlenecks in the system configuration To identify hardware requirements at the CSCs

June 2002REGNET Project Team Meeting Content Group 3 Methodology Performance testing objectives Pass / fail criteria Profiles of real users Test requirements Creation of test scripts and test execution Data gathering and correlation from the test tool and web / database server

June 2002REGNET Project Team Meeting Content Group 4 Performance testing objectives Find existing bottlenecks Verify current system capacity Verify scalability of the system Verify performance requirements Determine optimal hardware / application configuration

June 2002REGNET Project Team Meeting Content Group 5 Pass / fail criteria I (Proposal) Single transaction or single user: Successful completion of the test scripts without any failures and within the expected time allocation per transaction: Response time per page request < 1 seconds Multiple users carrying out multiple transactions in different roles: Successful completion of the test without any failures and within acceptable time per transaction / page delivery: Response time per page request < 5 seconds with up to 50 concurrent users A load test is successfully performed to validate performance to a minimum of 3600 different catalogue item requests hour A stress test is successfully performed to validate that the system and its single components do not reach their bottlenecks whilst serving pages to up to 100 concurrent users in different roles Tests are performed via LAN. Bandwith is not tested at this project stage. Bandwith monitoring can be used to determine necessary bandwith for production system. The database has its expected size These are very bold statements !!

June 2002REGNET Project Team Meeting Content Group 6 Pass / fail criteria II Web-server performance, the usability perspective Result page appearing time, Users View: < 0.1 s:User feels that the system is reacting instantaneously < 1.0 s:User experiences a slight delay but is still focused on the current website < 10 s:This is the maximum time a user keeps focused on a website, but the attention might already be distracted > 10 s:User is most likely distracted from the current website and looses interest Nielsen

June 2002REGNET Project Team Meeting Content Group 7 Profiles of real users (Proposal, to be discussed in Sofia) End user sends different requests to the system and views different items from the collection Special users performs different database functions (add, modify, delete) on single objects System administrator performs different database functions (add, modify, delete) on volume data Ratio of End User : Special User : System Administrator 22 : 2 : 1

June 2002REGNET Project Team Meeting Content Group 8 To Do´s in Sofia Estimation on test criteria Based on experience of current web- server usage rates Agreement on task assignement Agreement on test schedule

June 2002REGNET Project Team Meeting Content Group 9 To Do´s after Sofia Finalisation of test criteria Based on experience of current web-server usage rates Detailed user modelling (test scenarios) Test data gathering Software acquisition Set-up of test environement Test case implementation Carrying out of tests Results gathering Results evaluation + Recommendations Performance testing QA

June 2002REGNET Project Team Meeting Content Group 10 Technical test requirements Datasets are loaded onto the system / available for loading to perform different activities Different users exist in the system and have appropriate permissions Test hard- and software configuration PC running on Windows/NT, LINUX, etc., JDK1.2 or higher and jmeter installed, connected via LAN to the webserver A well equipped PC should be able to handle up to 100 concurrent threads (virtual users) Test scripts implemented Exclusive access to the system (1 night ?!) Access to server logs (processor usage, memory usage, disk I/O rates, network traffic) and jmeter logs

June 2002REGNET Project Team Meeting Content Group 11 Timeline (proposal) TBD