Search Results for "time"

...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 IDEs (CLion, Eclipse e.t.c) is straightforward. Using lazy algorithms there is virtually zero overhead in benchmarks and minimum overhead in execution time. ...

...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

...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.

This project born a few years ago when I encountered a fatal bug on a production environment, unfortunately not replicable on my development machine. I spent many time finding a solution, using also freeware and commercial third-party tools and libraries, but none helped me because the bug crashed the process, and no of the above tools could be able to catch the exception before the process dying. Also, it was not possible to install a development environment onto the production machines, so the only solution was to develop a debugger which didn't need any user/developer interaction. ...

The sandbox libraries (libsandbox & pysandbox) are an open-source suite of software components for C/C++ and Python developers to create automated profiling tools and watchdog programs. The API's are designed for executing and instrumenting simple (single process) tasks, featuring policy-based behavioral auditing, resource quota, and statistics collecting. The sandbox libraries were originally designed and utilized as the core security module of a full-fledged online judge system for...

FunctionCheck is a profiler for C/C++ programs, based on gcc V4.6.3+. Features are flat profile, cycles detection, call-graph, MIN/MAX time in functions, memory profiling, profiling control at execution...

This project is a tool for beginners to understand why a MPI program works or doesn't. It aims simple MPI codes, with a modest number of Processes. It is a real time view of an executing code, providing help even when the program deadlocks.

wtime is a small console program runs another program, then displays information about the resources(time/memory/IO) used by that program, collected by the system while the program was running. It works like 'GNU time', but is under Win32.

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.