OneStopTesting - Quality Testing Jobs, eBooks, Articles, FAQs, Training Institutes, Testing Software, Testing downloads, testing news, testing tools, learn testing, manual testing, automated testing, load runner, winrunner, test director, silk test, STLC

Forum| Contact Us| Testimonials| Sitemap| Employee Referrals| News| Articles| Feedback| Enquiry
 
Testing Resources
 
  • Testing Articles
  • Testing Books
  • Testing Certification
  • Testing FAQs
  • Testing Downloads
  • Testing Interview Questions
  • Career In Software Testing
  • Testing Jobs
  • Testing Job Consultants
  • Testing News
  • Testing Training Institutes
  •  
    Fundamentals
     
  • Introduction
  • Designing Test Cases
  • Developing Test Cases
  • Writing Test Cases
  • Test Case Templates
  • Purpose
  • What Is a Good Test Case?
  • Test Specifications
  • UML
  • Scenario Testing
  • Test Script
  • Test Summary Report
  • Test Data
  • Defect Tracking
  •  
    Software testing
     
  • Testing Forum
  • Introduction
  • Testing Start Process
  • Testing Stop Process
  • Testing Strategy
  • Risk Analysis
  • Software Listings
  • Test Metrics
  • Release Life Cycle
  • Interoperability Testing
  • Extreme Programming
  • Cyclomatic Complexity
  • Equivalence Partitioning
  • Error Guessing
  • Boundary Value Analysis
  • Traceability Matrix
  •  
    SDLC Models
     
  • Introduction
  • Waterfall Model
  • Iterative Model
  • V-Model
  • Spiral Model
  • Big Bang Model
  • RAD Model
  • Prototyping Model
  •  
    Software Testing Types
     
  • Static Testing
  • Dynamic Testing
  • Blackbox Testing
  • Whitebox Testing
  • Unit Testing
  • Requirements Testing
  • Regression Testing
  • Error Handling Testing
  • Manual support Testing
  • Intersystem Testing
  • Control Testing
  • Parallel Testing
  • Volume Testing
  • Stress Testing
  • Performance Testing
  • Agile Testing
  • Localization Testing
  • Globalization Testing
  • Internationalization Testing
  •  
    Test Plan
     
  • Introduction
  • Test Plan Development
  • Test Plan Template
  • Regional Differences
  • Criticism
  • Hardware Development
  • IEEE 829-1998
  • Testing Without a TestPlan
  •  
    Code Coverage
     
  • Introduction
  • Measures
  • Working
  • Statement Coverage
  • Branch Coverage
  • Path Coverage
  • Coverage criteria
  • Code coverage in practice
  • Tools
  • Features
  •  
    Quality Management
     
  • Introduction
  • Components
  • Capability Maturity Model
  • CMMI
  • Six Sigma
  •  
    Project Management
     
  • Introduction
  • PM Activities
  • Project Control Variables
  • PM Methodology
  • PM Phases
  • PM Templates
  • Agile PM
  •  
    Automated Testing Tools
     
  • Quick Test Professional
  • WinRunner
  • LoadRunner
  • Test Director
  • Silk Test
  • Test Partner
  • Rational Robot
  •  
    Performance Testing Tools
     
  • Apache JMeter
  • Rational Performance Tester
  • LoadRunner
  • NeoLoad
  • WAPT
  • WebLOAD
  • Loadster
  • OpenSTA
  • LoadUI
  • Appvance
  • Loadstorm
  • LoadImpact
  • QEngine
  • Httperf
  • CloudTest
  •  
    Languages
     
  • Perl Testing
  • Python Testing
  • JUnit Testing
  • Unix Shell Scripting
  •  
    Automation Framework
     
  • Introduction
  • Keyword-driven Testing
  • Data-driven Testing
  •  
    Configuration Management
     
  • History
  • What is CM?
  • Meaning of CM
  • Graphically Representation
  • Traditional CM
  • CM Activities
  • Tools
  •  
    Articles
     
  • What Is Software Testing?
  • Effective Defect Reports
  • Software Security
  • Tracking Defects
  • Bug Report
  • Web Testing
  • Exploratory Testing
  • Good Test Case
  • Write a Test
  • Code Coverage
  • WinRunner vs. QuickTest
  • Web Testing Tools
  • Automated Testing
  • Testing Estimation Process
  • Quality Assurance
  • The Interview Guide
  • Upgrade Path Testing
  • Priority and Severity of Bug
  • Three Questions About Bug
  •    
     
    Home » Testing Articles » Load, Stress & Performance Testing Articles » Load testing - real world experience.

    Load testing - real world experience.

    A D V E R T I S E M E N T


    A survey was taken in three of Toronto's companies that specialized in load testing and using the different, but most popular load testing tools.

    The result of the survey will be more interesting after reading some important points about Load testing and Load testing tools that may be interesting even before beginning evaluation of particular tool.

    1. There is a lot of tools for load testing from free to very expensive tools. For example LoadRunner from Mercury Interactive may cost $40,000 for only 50 concurrent users. The real price may grow up to $150,000 with reasonable number of concurrent users.

    2. Is the tool you choose suitable for your application and your environment? What is the evaluation and learning period for the tool?

    3. These tools support only certain protocols (be careful if you are working with Tuxedo) and platforms. SilkPerformer currently supports only Windows NT and Windows 2000.

    4. Do the tools’ own processes, running at the same time with testing, have an influence on the application’s performance? Assume about 3 MB of RAM for every concurrent user. In my case 512 MB of RAM did not allowed me to run more then 100 users.

    5. Do not forget that tools have their own bugs. In our case we had a real time money transaction and the tool we tried could only send requests but didn’t wait for a system response.

    6. It is necessary to pay attention (and every experienced QA person understands it) to the fact that without a proper testing scenario and definition of the load points of system architecture all the results may be not precise.

    7. Pay attention on the exact influence of the mirror sites and the network system on your tests. Do you load the production environment or only your own network system?

    8. Scaling down the production environment for creating Load test environment is a great idea. But is there a linear correlation between the results in the testing and real environments? Pay great attention to all details during designing and creating of testing environment.

    9. Nortel wishes everyone had optical pipes running everywhere, the equivalent of adding a 20 meters width channel build across Toronto. What happens in traffic when a stranger is trying to move from one location to another? Does anybody have an idea? Even Sherlock Holms will not investigate this problem.

    Results of this survey show that most problems can be found using from 2 to 10 concurrent users or VU (virtual users). Increasing the number of VU until 200-250 by buying additional licenses did not discover additional problems. 250 VU may help to find problems sooner without thinking and studying the application, but this is not the right method – from my point of view. All discovered problems were related to database locks, pure OO design, coding and implementation. Some researches show that it is possible to find out the maximum number of simultaneous connections by writing a code. Connections must be created for every of the following load points: Database, Web Server, Application Server, Router, Firewall, Hosting Company’s Network. This method allows testing the system for scalability. While running this code, I suggest testing applications manually for performance and functionality. These allow finding bottlenecks and checking scalability of the system, without using expensive tools and with the same accuracy. To check what ports you need to load –simply type “netstat –na | more” in command prompt. Now you can use different types of loading:
    1. Send garbage data to an open file sharing port 139 on windows machine.
    2. Use UDP to load ports 69, 161, 7070
    3. Use TCP to load Port 21 (FTP)
    4. In additional you can try to load Port 23 –Telnet, Port 25 – SMTP, Port
    666 – Doom and of course Port 80 HTTP
    For loading you can use free tools for ports scanning like NmapNT or Nmap or create different types of packets and be smarter making packets none of which have a fragment offset of zero or be set to incorrect values. You can try to oversize ping packets.



    More Load, Stress & Performance Testing Articles
    Previous 1 2 3 4 5



    discussionDiscussion Center
    Discuss
    Discuss

    Query

    Feedback
    Yahoo Groups
    Y! Group
    Sirfdosti Groups
    Sirfdosti
    Contact Us
    Contact

    Looking for Software Testing eBooks and Interview Questions? Join now and get it FREE!
     
    A D V E R T I S E M E N T
       
       

    Members Login


    Email ID:
    Password:


    Forgot Password
    New User
       
       
    Testing Interview Questions
  • General Testing
  • Automation Testing
  • Manual Testing
  • Software Development Life Cycle
  • Software Testing Life Cycle
  • Testing Models
  • Automated Testing Tools
  • Silk Test
  • Win Runner
  •    
       
    Testing Highlights

  • Software Testing Ebooks
  • Testing Jobs
  • Testing Frequently Asked Questions
  • Testing News
  • Testing Interview Questions
  • Testing Jobs
  • Testing Companies
  • Testing Job Consultants
  • ISTQB Certification Questions
  •    
       
    Interview Questions

  • WinRunner
  • LoadRunner
  • SilkTest
  • TestDirector
  • General Testing Questions
  •    
       
    Resources

  • Testing Forum
  • Downloads
  • E-Books
  • Testing Jobs
  • Testing Interview Questions
  • Testing Tools Questions
  • Testing Jobs
  • A-Z Knowledge
  •    
    Planning
    for
    Study ABROAD ?


    Study Abroad


    Vyom Network : Free SMS, GRE, GMAT, MBA | Online Exams | Freshers Jobs | Software Downloads | Programming & Source Codes | Free eBooks | Job Interview Questions | Free Tutorials | Jokes, Songs, Fun | Free Classifieds | Free Recipes | Bangalore Info | GATE Preparation | MBA Preparation | Free SAP Training
    Privacy Policy | Terms and Conditions
    Sitemap | Sitemap (XML)
    Job Interview Questions | Placement Papers | SMS Jokes | C++ Interview Questions | C Interview Questions | Web Hosting
    German | French | Portugese | Italian