Search Results for "j-trace"

Kieker is a framework for continuous monitoring and dynamic analysis of distributed software systems. Being designed for continuous operation, it induces only a low overhead. The TraceAnalysis tool allows to analyze and visualize trace information.

The openresty-systemtap-toolkit is a collection of SystemTap-based scripts designed for real-time analysis and diagnostics of OpenResty and its core components, including NGINX, LuaJIT, and ngx_lua. It provides developers and system administrators with tools to trace performance bottlenecks, memory usage, request distribution, regex execution, Lua execution, and file I/O behaviors in production systems. The toolkit helps identify leaks, analyze TCP queues, inspect shared memory usage, and generate flame graphs for CPU and off-CPU profiling. Many scripts are specific to NGINX worker and master processes, while others are generic enough to be applied to any Linux user-space process. ...

Insanely fast, headless full-stack testing using Node.js. Zombie 6.x is tested to work with Node 8 or later. If you need to use Node 6, consider using Zombie 5.x. If you’re going to write an insanely fast, headless browser, how can you not call it Zombie? Zombie it is. Zombie.js is a lightweight framework for testing client-side JavaScript code in a simulated environment. No browser required. Zombie will work with other testing frameworks. Since Mocha supports promises. Just like your...

The alio library can be dynamically pre-linked to existing executables and replaces file IO (i.e. calls to glibc's IO functions). This allows to gather statistics about IO, create IO trace files, or even implement a different IO behaviour (e.g. use separate IO servers to handle IO).

A little tool writen in java to trace the execution plan for a given database query. It works with Oracle 10g or higher and uses the JGoodies look and feel. You need to provide the Oracle.com JDBC-Driver and the JGoodies.org looks look and feel. Source is now located at Github https://github.com/mgeiss/oraxtra.

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.