Search Results for "memory database"

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

sysbench is a scriptable multi-threaded benchmark tool based on LuaJIT. It is most frequently used for database benchmarks, but can also be used to create arbitrarily complex workloads that do not involve a database server. extensive statistics about rate and latency is available, including latency percentiles and histograms. Low overhead even with thousands of concurrent threads. sysbench is capable of generating and tracking hundreds of millions of events per second. New benchmarks can be...

Aqueduct is a modern Dart HTTP server framework. The framework is composed of libraries for handling and routing HTTP requests, object-relational mapping (ORM), authentication and authorization (OAuth 2.0 provider) and documentation (OpenAPI). These libraries are used to build scalable REST APIs that run on the Dart VM. An object-oriented, multi-threaded HTTP server framework written in Dart. Aqueduct is an extensible HTTP framework for building REST APIs on top of the Dart VM. It includes a...

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.

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

Copies the schema from one DB to another - present primary use is to set up an in-memory DB that replicates the structure of a particular tablespace of a network-accessible (e.g. Oracle) database so that unit tests run much faster. In use since 2003.

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.