Search Results for "run time java"

Libinstrument is a complete and easy way to do custom function instrumentation for C/C++. The project comes ready with classic applications of instrumentation, such as AOP (Aspect Oriented Programming), Concern and Side Effect injection, stack tracing, exception tracing, basic time profiling, callgraph profiling and other. A GC (Garbage Collector) module is also under development. Libinstrument is highly portable and decoupled. The project comes with a CMake build system, integration with...

...The flow does not assume any specific parallelization technique, thus it can be broadly applied. The original (serial) C source is automatically annotated to trace the execution profile and data dependencies at run-time. The annotated program is then executed using a significant (but small) data set selected by the developer. The data collected is cross-referenced with the original source and can be interactively analyzed graphically to determine the best parallelization candidates and techniques.

Shiny is a lightning fast, fully documented & by-far-easiest-to-use C/C++/Lua profiler with no extensive surgery. Results are smoothed & shown in run-time as a call-tree or sorted-by-time. Output also renderable as graphs in Ogre3D or your custom engine

SLOCCount is an easy-to-use tool that counts Source Lines of Code (SLOC). It auto-determines the language(s) (inc. C, C++, Ada, Assembly, shell, COBOL, C#, Fortran, Haskell, Java, LISP/Scheme, Perl, PHP, Python, Ruby, SQL). It also estimates cost & time.

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.

An implementation of the Open Group's Application Response Measurement (ARM) Version 4 standard. The ARM standard describes a means of breaking an application down into it's constituent transactions, and measuring response time across multiple tiers.

This profiler (JRE 1.5.0 only) uses JVMTI and native bytecode instrumentation for the analysis of the heap, reachable objects, execution time, garbage collection efficiency, code coverage and thread contention. No preparation steps required in build.