You are viewing an old version of this page. View the current version.
How to optimize your local machine for the Kiuwan Local Analyzer (KLA)
Every analysis step is accomplished by executing a new JVM.
Below follows some considerations you must bear in mind to properly configure your analyses.
Java Virtual Machine
Every step is performed through the execution of a JVM process.
Java 8 (64 bits) or above —either JDK or JRE— is required.
For Linux/Unix usersIcon
IMPORTANT for LINUX/UNIX users:
Please check /dev/random configuration of JVM. This may produce severe performance problems (java urandom Entropy).
Below link will help you to fix it:
By default, KLA comes with pre-configured default values:
max memory to use during every single step
max duration time (timeout) of every single step
These parameters are configured through KLA configuration mechanism, please do not modify KLA scripts to include JVM flags such as -Xmx, use the mechanisms Kiuwan provides.
Single and parallel execution of analyses
Every Kiuwan analysis executes sequentially, i.e. every step is executed sequentially and following the order specified below:
For each technology
Report generation, encryption and uploading to Kiuwan cloud
Every step is executed by a “new” JVM, and Kiuwan configuration applies to all of those JVM instances.
Therefore, those memory-cpu consuming steps may result in full use (near to 100%) of a CPU core.
If the machine running KLA analyses contains more available CPUs, you can run “simultaneous” (or parallel) analyses by executing additional instances of KLA.
In a parallel KLA execution scenario, every running analysis is completely independent from each other, so you can execute multiple analysis provided your machine has enough CPUs.
By default, KLA comes pre-configured with the following memory default values (analyzer.properties):
If you notice that your local analysis ends with an Out of Memory (OOM) error, you need to increase the max memory allocated to the JVM (by default, 1Gb).
Below troubleshooting links can help you to identify OOM errors:
You can configure Kiuwan to increase memory limits either for the whole installation or per application.
- If you are using Kiuwan GUI, please visit https://www.kiuwan.com/docs/display/K5/Kiuwan+Local+Analyzer+GUI+-+Graphical+User+Interface#KiuwanLocalAnalyzerGUI-GraphicalUserInterface-AnalysisConfigurationtab
- If you uses CLI , please visit https://www.kiuwan.com/docs/display/K5/Kiuwan+Local+Analyzer+CLI+-+Command+Line+Interface#KiuwanLocalAnalyzerCLI-CommandLineInterface-Mostcommonlyconfiguredparameters
Depending on your available physical memory available, OS and JVM version, if you increase the max memory the JVM might not start (please see https://www.kiuwan.com/docs/display/K5/Not+enough+Memory).
In these cases, stopping unneeded processes (or restarting the machine) can free unneeded allocated memory. Nevertheless, sometimes this does not free memory so you need to test with lower memory values.
Although you were not getting an OOM, if you notice the process is performing a high activity of JVM garbage collection, this situation may indicate your analysis needs more memory and the performance is suffering due to gc activity. In theses cases, try to increase the max memory, most probably the analysis performance will be faster.
Do not increase indefinitely the memory.
If you see that your analysis needs more than 2GB to finish, it might be a clue of an existing memory leak or some other strange situation.
In this case, do not hesitate to contact Kiuwan Technical Support and report this situation.
By default, every step of a local analysis is configured to a default max execution time (60 minutes) (analyzer.properties):
The default value is often enough for most of the analyses, but depending on several circumstances (code size, memory, ruleset, etc) could not be enough and a timeout error will occur (Timeout killed the subprocess).
If this happens, you can increase the default value.
- No labels