To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at

If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

The first impression of Intel Parallel …

The first impression of Intel Parallel Inspector

May 18 2009

I experimented with Intel Parallel Inspector in memory-error diagnosis mode. I can say that I liked the product and the work it does. I was especially impressed by perfect integration into Visual Studio and full support of 64-bit projects—which Bounds Checker users will appreciate.

Mostly, I experimented with the Viva64 project and managed to find one rather serious error.

I liked the graphical interface of the Parallel Inspector launch mode settings very much—it is simple and clear:


I liked the indicator showing how much the current analysis type can slow down a program's execution. I liked this approach, the design and clearness of what to expect so much that I decided to check this indicator's accuracy on Viva64 project. Of course, the sampling is unrepresentative, but the check was still very interesting. Here are the results of launching the 64-bit debug-version of Viva64:

Launch mode

Expected slowdown, according to the Parallel Inspector scale

Actual slowdown when testing the Viva64 project

Without Parallel Inspector

No slowdown

(1.23 sec) – No slowdown

"Does my target leak memory?"

By 2 - 20 times

(17.70 sec) – by 14.4 times

"Does my target have memory access problems?"

By 10 - 40 times

(72.57 sec) – by 59 times

"Where are the memory access problems?"

By 20 - 80 times

(70.80 sec) – by 57.6 times

"Where are all the memory problems Inspector can find?"

By 40 - 160 times

(404.82 sec) - by 329.1 times

I think that the slowdown estimate is pretty close for cases when there is no information about the project. In the last mode, the figures I got exceeded the expected result. However, the Viva64 analyzer, compared to an average program, has a lot of memory allocation operations. Viva64 needs them when building and analyzing the syntax tree. So an increase in slowing, as compared to the estimate, is expected.

Using Intel Parallel Inspector leads to slowdowns, but they do not worry me. I consider them natural and not even that significant for a dynamic analysis tool that offers these features. However, it's a good thing to remember that it can be best to avoid running this tool for a program in real time. A more efficient approach would be to use packet launches or automated testing systems that will run at night and click all the buttons in an application. This way, you will not need to worry that the response may take minutes or hours.

All in all, I found Intel Parallel Inspector very useful and highly recommend it.

Popular related articles
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →