Quality Testing

Quality is delighting customers

Hi All,


I need some information about Scalability Testing? Anybody having documnets, share me plz. 


It is very urgent.


~Jelissa

Views: 720

Reply to This

Replies to This Discussion

Load Testing - Testing an application under heavy loads,such as testing of a web site under a range of loads to determine at what point the sytem's response time degrades or fails.

Scalability Testing - Scalability testing differs from Load Testing in that it focuses on the performance of your Web sites, hardware and software products, and internal applications at all the stages from minimum to maximum load.

First of all its important to know what you are scalability testing for.  Generic documents arent going to help you.  @Malay's reply highlights common error, people often confuse load and performance testing. Scalability testing is not something to appraoch lightly, and needs careful defintion and planning, if results are going to be worthwhile.  So provide some more detail, then maybe can give some useful advice.

@Malay

 

Thanks for your reply, but I know these definitions. I am looking for some thing real time answer, what is scalability  and how to use in project. 

 

I am having a presentation on Monday, if you are having any such type of information, please share me.

 

@Jaffamonkey,

 

I am having presentation on Monday (18th July 2011).

 

Topic: Scalability Testing

 

I don't want definitions, I am looking for some thing real time scenarios. 

 

Thanks in advance.

 

~Jelissa

 

 

Not something I usually do - but since you have a presentation, I will see what I can dig out for you :) Also check out the linkedin forums. 

 

This link is an extremely basic example of scalability testing but nice example of how important benchmarks are for scalability testing:-http://geoserver.org/display/GEOS/Performance+and+Scalability+Testing

In order to effectively plan for scalability testing, you need benchmarks for comparisons (in this extremely basic example, its image load times for diferent map zoom levels).  So that is first activity - what areas of the application are of interest for scalability testing.  Common scalability focus area is page rendering on a website, and its performance when under incremental amounts of user activity. 

 

To be honest, load and scalability testing have many crossover points - and they are both focussed of indentifying limits and weaknesses of an application.  As you will notice from defintions in comment earlier, the statements are different, but also the same!  Will see what else I can dig out for you.  Feel free to add me on linkedin!  I spend more time on there.

Dear Jaffa,

 

Really thanks for providing this link, hope this will help me for preparing scalability presentation.

 

Thanks,

Jelissa

If you are doing a presentation on it, then better to keep examples simple anyway - will see if I can find a few other small examples, then it won't be so overwhelming to present.  Worth noting also (though you will find a lot of contradictory definitions on these), is that Scalability testing, Volume testing and Load testing all come under Performance Testing.  And that makes logical sense. And I would argue that if you do one of these, you end up covering all three as the activities are similar.

 

Scalability testing is focused on ensuring the application under test gracefully handles increases in load.  Therefore the work that is needed is is to generate traffic, and ideally realistic traffic.  Then monitor the backend servers for performance-related issues.  So, using an automated test tool, you could script individual front-end tests for:-

Searching

Page loading time

Registration

Login

etc...

Then use load test tool to use these scripts, emulating multiple users, performing these scripts, in a timed and controlled way.  It is important to ramp up the tests slowly, in order to allow system monitors to highlight problems early, rather than ending up with system crash. Softly, Softly :)  The aim of scalability testing is exactly what it suggest - testing scalability of the system, i,e. at what points does the application start to creak under the pressure.  The backend monitoring is critical to success - the more information, the more structured the testing, the more valuable the results.

The extent of this list above depends on the features available in application under test.  Also, to monitor effects of the system, use a profilers to monitor and report on: database activity, application server, and web server (assuming this is a web application).

You got me on a good day :)

Hi Jelissa,

I just try with different answer. Go through it . I have also uploaded one pdf file.

Just check it.

Scalability testing lets you determine how your application scales with increasing workload.

Suppose, your company expects the six-fold load increase on your server within the next two months. You may need to increase the server performance and shorten the request processing time to better serve visitors. If your application is scalable, you can shorten this time by upgrading the server hardware, for example, you can increase the CPU frequency and add more RAM (also, you can improve the request performance by changing the server software, for example, by replacing text-file data storages with SQL Server databases. To find a better solution, first, you can test hardware changes, then software changes and after that compare the results of the tests).

Scalability testing can give answers to the following typical questions:

  • How do hardware and software changes affect the server performance?
  • Is it possible to increase the application’s productivity by upgrading the server hardware?

=========================================

 

SCALABILITY TESTING ATTRIBUTES
Following are the only few attributes out of many that considered during the scalability
testing
Response Time
Throughput
Screen transition
Time {Session time, reboot time, printing time, transaction time, task execution time}
Hits per second, Request per seconds, Transaction per seconds
Performance measurement with number of users.
Performance measurement under load.
CPU usage Memory usage {Memory leakages, thread leakage} Bottlenecks {Memory,
cache, process, processor, disk and network}
Network Usage {Bytes, packets, segments, frames received and sent per sec, Bytes
Total/sec, Current Bandwidth Connection Failures, Connections Active, failures at
network interface lever and protocol level}
Web server {request and response per seconds, services succeeded and failed, server
problem if any}

Attachments:

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2020   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service