Search Results for "static code analysis"

PerfView is a free performance analysis tool that helps isolate CPU and memory-related performance issues. It is a Windows tool, but it also has some support for analyzing data collected on Linux machines. It works for a wide variety of scenarios, but has a number of special features for investigating performance issues in code written for the .NET runtime. If you are unfamiliar with PerfView, there are PerfView video tutorials.

TimerOutputs.jl is a lightweight Julia package that provides a structured way to measure and report the execution time of different parts of code. It is particularly useful for performance profiling in scientific computing, allowing developers to annotate sections of code and generate readable timing summaries. TimerOutputs.jl supports nested timers and formatted output to both terminal and files, helping users easily identify bottlenecks in their programs.

Node Clinic is a suite of diagnostic tools for Node.js applications, designed to help developers identify and resolve performance issues, memory leaks, and other common problems in their code.

gcRadar is not a static code anayser but it is a library using which is ment to beused in your source code and it will monitor and report the lifetime events of yuor objects. gcRadar can provide this information by using callbacks, log4j & polling. gcRadar can monitor entities ranging from individula objects to full object trees comprising of is-a & has-a relationships.

A collection of library code and tools for application execution profiling and performance testing. You can create stopwatches to time select portions of your code. You can measure differences (often to sub-millisecond accuracy) between clocks on different machines. You can log application events in a .csv format for subsequent analysis. You can also generate CPU loading logs in a .csv format.

Note: this tool has moved to github, this repository is not maintained any more. See https://github.com/turdusmerula/ftrace GScopeLog is a tool for instrumenting c++ code through gcc. The main purpose is to trace entry/exit point of functions. A status file may be generated to give overview of functions calls and timing informations with minimal impact on performances.

This is a simple, modular PHP class designed to record execution time benchmarks throughout different parts of a script. Compatible with virtually any PHP script, the code can be added/removed quickly and with ease. Accurate to the microsecond.