Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Slow performance in Klocwork Static Code Analysis

Slow performance in Klocwork Static Code Analysis can be the result of poor database performance. If you have many Klocwork projects and builds, you might want to tune the Klocwork database settings. See Improving database performance.

Some virus scanners may slow analysis performance

If certain virus scanners are deployed (such as Trend Micro Worry-Free Business Security 6.0), your analysis time may increase. If your anti-virus software permits, configure exclusion folders for the projects_root directory and the tables directory.

"Tracker" plug-in for GNOME may cause performance drop in full analysis Unix only: Running the Tracker search tool for GNOME may significantly slow a full Klocwork analysis.Workaround: Disable Tracker when running a Klocwork analysis.