Search Results for "memory"

Zerocopy is a Rust library designed to make zero-cost memory manipulation both safe and effortless. It allows developers to reinterpret or convert raw byte sequences into structured types—and vice versa—without writing unsafe code directly. The crate provides safe abstractions for transmuting data while preserving Rust’s strict safety guarantees, removing the need for manual memory manipulation.

This benchmark suite is intend as a tool for the research community. It consists of a set of open source, real world applications with non-trivial memory loads.

UVU is a lightweight, ultra-fast JavaScript test runner for Node.js and the browser created by Luke Edwards (lukeed). Its primary goal is to minimize overhead: startup time, memory usage, and complexity are all kept very low so that developers can write and run tests with minimal friction. The tool supports modern features like async/await and native ES Modules, making it suitable for modern codebases. It also supports running in browser environments, which makes it versatile for frontend and backend alike. ...

Log4db2 is a logging utility for DB2 LUW that uses SQL instructions with SQL PL code. Its purpose is to provide an easy way to write messages from a SQL routine, with the possibility to query these messages directly from the database, allowing to monitor the progression of a process. This utility aims to reduce the time used for developing, testing, debugging and monitoring SQL routines, by centralizing the messages produced by the code. The idea and architecture of this utility...

...Rather than synthetic micro-benchmarks, it packages build scripts, corpora, and known-crash oracles so fuzzer authors can measure time-to-crash, coverage growth, and stability. Each target is configured to integrate with common sanitizers, ensuring memory safety bugs surface with precise diagnostics. The suite standardizes experiment parameters—runtime, seeds, and environment—so results are reproducible and comparable across machines and research groups. It’s useful both for tuning mutation strategies and for validating new coverage mechanisms before publishing results. By curating diverse targets (parsers, media codecs, serialization libraries), it helps fuzzers demonstrate robustness beyond a single niche.

memory-stats.js is a small JavaScript utility that displays page memory usage in a style similar to stats.js. It was inspired by mrdoob’s stats.js and originally came from work related to tquery before becoming a standalone repository. The tool helps developers monitor JavaScript memory behavior directly inside a web page during development or debugging.

A Python programming environment providing memory sizing, profiling and analysis, and a specification language that can formally specify aspects of Python programs and generate tests and documentation from a common source.

...SAR is cumulative activity counters in the operating system. It is the most comprehensive command which helps to monitor performance of various Linux / Solaris subsystems (CPU, Memory, I/O, Disk, Network, etc) all in same log. This makes it difficult to analyze since every counter data is dumped into the log file. SarBox helps to analyze this log file and present data in graphical charts or text format. To collect sar statistics from an environment, use below syntax [user@host ~]# sar -A 30 2 > sar_linux.log “30 2” reports for every 30 seconds and total of 2 times, written in sar_linux.log.

Stand alone Java application used simulate a memory leak in order to generate profile signatures. The application has the ability to generate system (CPU) load in order to observe profile signature changes.

jLlama is a desktop application to monitor servers over SSH. Any figure retrieved from the command line can be polled and graphed in real time. Out of the box, jLlama can graph CPU and Memory usage for Linux and Solaris servers.

Objectreferenceanalyser (ORA) helps finding memory leaks, design weaknesses and bugs. The ORA-Framework visualizes objects, their content and relations during runtime of any Java application and is able to persist these findings for subsequent analyze.

An open-source desktop application for load/performance testing a web site. It has a very simple UI to configure the load test. The future plan includes transaction support, record, playback and support for load injector agents.

Stopwatch is a simple, highly extensible, API that alows monitoring of any part of the application. It reports hits, execution times and load but can be extended to do more via custom engines. It is able to persist data in "in-memory" or real database.

ebizzy is designed to generate a workload resembling common web application server workloads. It is highly threaded, has a large in-memory working set, and allocates and deallocates memory frequently.

A easy to use memory debugger lib for C++ projects. Tracks and logs (if desired) memory allocations, deallocations, memory leaks. A support template class is also provided to check for memory invasions in dynamically allocated memory using operator [].

Jdptool is a debug and profiler tool which based on JPDA; It provide both swing based and browser based GUI. It has sophisticated debugger without user interfere. It also provide profiler to memory usage and threads with numerous new feature

An Extensible memory leakage detection system which can be turn on/off just including or not a C header

Toplink in memory makes TDD possible in large database applications. Make your Java project tests run faster. Toplink in memory allows you to run your tests in memory, rather than against a database. In our current project, this gives a 100x speed up.

AdaptiveCells J2EE generates test-beds for benchmarking J2EE performance. They consists of highly customizable EJB cells that can emulate CPU load, memory usage, memory leaks and exceptions. The behaviour of the cells is coordinated from a web front-end.

Test Connect provides monitoring and trend tracking of memory, CPU, etc. on kernel level code on multiple platforms. Used with every build Test Connect can provide insight into how code is behaving, or misbehaving, with system resources or memory.