What is rational purify and rational quantify?

Explain in step by step

Replies to This Discussion

Permalink Reply by Someswara Rao on May 1, 2008 at 10:06am

Hi,

Rational Purify and rational quantify are used to diagnose the application under test for memory errors,leaks and performance bottlenecks and gaps in code coverage during testing

▶ Reply

Permalink Reply by Kumar on May 2, 2008 at 2:22pm

Rational Quantify: This component will help rational robot to find speed and efficiency of the application

Rational Purify:This component is used to avoid memory leakage due to the use of pointer concept in c&c++

▶ Reply

Permalink Reply by MAK on October 21, 2008 at 11:57am

Hi

Rational Purify is a testing tool which are mostly used by developer in order to check Memory Related Error
Some of the errors that are detected using Rational Purify are - Memory Leak, Array Bond Errors,Uninitialized Memory Reads,Uninitialized Memory Write etc
Rational Purify gives you the correct LINE NO where the above errors are occuring

Rational Quantify is again a developer tool which help in find out the efficient of the code which the coded have coded.

Rational Purify,Rational PureCoverage and Rational Quantify are called as Rational PurifyPlus

▶ Reply

Permalink Reply by Indu on June 25, 2009 at 6:04pm

Hi,

Rational Purify
IBM Rational Purify is a runtime analysis solution designed to help developers write more reliable code. Reliability is ensured via two crucial functions: memory corruption detection and memory leak detection. Rational Purify packages support for these two runtime analysis capabilities in a single product with a common install and licensing system.

Rational Purify Plus :
IBM® Rational® PurifyPlus is an award-winning dynamic analysis solution designed to help developers write faster, more reliable code.
It includes four basic capabilities packaged into a single product:
1) Memory debugging (pinpoints hard to find memory errors such as uninitialized memory access, buffer overflow and improper freeing of memory),
2) Memory leak detection (identifies memory blocks that no longer have a valid pointer),
3) Performance profiling: (highlights application performance bottlenecks and improves application understanding with a graphical representation of function calls) and
4) Code coverage (identifies untested code with line-level precision). PurifyPlus is supported on Windows, Linux, Solaris, AIX and HP-UX.

Rational Quantify

What it does
Your application's run-time performance-its speed-is one of its most visible and critical characteristics. Developing high-performance software that meets the expectations of customers is not an easy task. Complex interactions between your code, third-party libraries, the operating system, hardware, networks, and other processes make identifying the causes of slow performance difficult.
Rational® Quantify® is a powerful tool that identifies the portions of your application that dominate its execution time. Quantify gives you the insight to quickly eliminate performance problems so that your software runs faster. With Quantify, you can:

Get accurate, repeatable performance data

Control how data is collected, collecting data for a small portion of your application's execution or the entire run

Compare before and after runs to see the impact of your changes on performance

Easily locate and fix only the problems with the highest potential for improving performance
Unlike sampling-based profilers, Quantify's reports do not include any overhead. The numbers you see represent the time your program would take without Quantify. Quantify instruments all the code in your program, including system and third-party libraries, shared libraries, and statically linked modules.
This chapter introduces the basic concepts involved in using Quantify. For complete information, see the Quantify online help system.

How Quantify works
Quantify counts machine cycles: Quantify uses Object Code Insertion (OCI) technology to count the instructions your program executes and to compute how many cycles they require to execute. Counting cycles means that the time Quantify records in your code is identical from run to run, assuming that the input does not change. This complete repeatability enables you to see precisely the effects of algorithm and data-structure changes.
Since Quantify counts cycles, it gives you accurate data at any scale. You do not need to create long runs or make numerous short runs to get meaningful data as you must with sampling-based profilers-one short run and you have the data. As soon as you can run a test program, you can collect meaningful performance data and establish a baseline for future comparison.

Quantify times system calls: Quantify measures the elapsed (wall clock) time of each system call made by your program and reports how long your program waited for those calls to complete. You can immediately see the effects of improved file access or reduced network delay on your program. You can optionally choose to measure system calls by the amount of time the kernel recorded for the process, much like the /bin/time UNIX utility records.

Quantify distributes time accurately: Quantify distributes each function's time to its callers so you can tell at a glance which function calls were responsible for the majority of your program's time. Unlike gprof, Quantify does not make assumptions about the average cost per function. Quantify measures it directly.

You can get more articles like this from Macrotesting