Search Results for "time code"

Webgrind is an Xdebug profiling web frontend for PHP, offering a lightweight and easy-to-use interface to visualize profiling data. It helps developers identify performance bottlenecks in their applications by displaying function call statistics, memory usage, and execution time. Webgrind is ideal for performance analysis and optimization of PHP code, providing insights into code efficiency.

py-spy is a sampling profiler for Python programs. It lets you visualize what your Python program is spending time on without restarting the program or modifying the code in any way. py-spy is extremely low overhead: it is written in Rust for speed and doesn't run in the same process as the profiled Python program. This means py-spy is safe to use against production Python code. py-spy works from the command line and takes either the PID of the program you want to sample from or the command line of the python program you want to run. py-spy has three subcommands record, top and dump. py-spy supports recording profiles to a file using the record command. ...

Luke StackWalker is a GUI-based C/C++ source code profiler for Windows. It samples your application's stack while the application is running to find out where the application spends most of its time.

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

Scenario is a very simple yet neat and powerful tool for loading and managing JS scripts. Scenario is very useful for the following cases: 1. Unit testing for JS without reloading the web page and re-engineering your code. 2. Load and manage scripts stored in arrays (code management). 3. Optimize coding flow by dynamically switching among best solution per case. 4. Run scenarios either distinctly or in parallel. 5. Keep easier track of bugs and errors when deploying. So, Scenario executes multiple views of your code or multiple scenarios of your code life-time on-demand.

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.

A Ruby file parser/interpreter/preprocessor that comments lines of code based on conditions at the time the file is required. Very handy to implement debugging logs and code that has to be commented (not just dynamically switched off).

Rapidlogix is an open source application performance management tool optimized for distributed production environments. It allows to increase time-to-market of performance improvements and prevent performance regression

FreeProfiler is a C++ performance profiler. Compared to other profilers, It has smaller granularity. It focuses on code blocks and messages. So user knows exactly how much time is consumed by a specific message or a part of a function.

Orate is a source-level tracing facility for Oracle PL/SQL. Programmers insert calls to Orate in the code and Orate captures and writes run time information to a table. These data are suitable for debugging, testing and profiling the application.

This project is designed to help programmers understand the resource utilization of their code in the Java Virtual Machine and provide real time feedback via a GUI interface.

Z80 ASM editor that gives you real-time info about Mnemonics, Waitstates/Clock cycles, and Labels. Features code completion, real-time debugging and T-states profiling.

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.