To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an 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.

Many cores are good but a fast hard dis…

Many cores are good but a fast hard disk is good too

Dec 28 2009

Developing the code analyzer PVS-Studio we consider the task of increasing the tool's performance. Such solutions are quite slow, so the programmer who possesses even a powerful computer sometimes gets bored while waiting for the analysis to be completed. PVS-Studio analyzer employs the abilities of multi-core processors and it allows you to increase the speed of analysis of a project in several times in comparison to single-core systems. However, it turned out that the disk subsystem may also impact the analysis speed.

We have a base of regression tests of about 30 applications (more than 90 projects) - these are the source codes that are tested by the analyzer PVS-Studio in automatic mode. The testing of all these codes by the analyzer's version for Visual Studio 2008 takes about two hours. We use a machine with the following characteristics: two-core processor, 4 Gbytes of memory and SATA RAID-system (RAID 0). This computer has also an old IDE hard disk installed that has not been used in any way but there has been no occasion to remove it.

Once, due to some reason, the tests were moved from SATA RAID to IDE. After that, it took us a long time to understand why the tests now executed four hours instead of two! The point is that the tests had been moved at the same time we had made some serious changes in the product and it seemed to us that it was these changes that caused such a great performance drop. But we recalled soon that we had switched to a second hard disk and the problem found its solution.

In what way does a hard disk relate to the code analyzer? In the most direct one. When the analyzer is working the preprocessed files of all the source codes are created and the analyzer works with them then. We counted the size of the preprocessed files in our tests for Visual Studio 2008 and it appeared to be about 7 Gbytes. Of course reading/writing of such a size on an old IDE disk causes a crucial performance drop.

The conclusion is simple: when performing compilation, and all the more when working with code analyzers, keep the source codes on a fast SATA disk, or, even better, use a RAID array. And work will become much more pleasant.

Popular related articles
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…
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…
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…
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…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
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…
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…

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 →