Search Results for "working memory" - Page 2

CCM is a solution for the data management layer in the combination of Sql Server with a C # application. In whole this is a strongly typed entity mapper projecting the application's business logics onto database tables using T-SQL stored procedures. CCM allows you to implement fairly complex data structures in your application, without bothering about difficult and tedious questions of data acquisition and conversion issue, allowing you to pay more attention to the develop of business logic...

quire is a scripting language for performing calculations on information from genetic experiments. Although quire is capable of performing arbitrary calculations, it is really a domain-specific language driven by convenience in working in the problem domain over speed or memory usage. quire has a facility to add in binary modules to perform more intensive calculations.

...What's completed? As of writing, the following libraries have been written and tested: 1. Memory accounting/tracking 2. String operations 3. Vectors 4. Trees 5. Dictionary arrays 6. Configuration management See the wiki page for more information

gitfs is a FUSE file system that fully integrates with git. You can mount a remote repository's branch locally, and any subsequent changes made to the files will be automatically committed to the remote. gitfs was developed by the awesome engineering team at Presslabs, a Managed WordPress Hosting provider. gitfs was designed to bring the full powers of git to everyone, no matter how little they know about versioning. A user can mount any repository and all their changes will be automatically...

...You can profile any function in your code. Furthermore, this library provides measuring time of any block of code. For example, information for 12 millions of blocks is using less than 300Mb of memory. Working profiler slows your application execution for only 1-2%. The average overhead per block is about 15ns/block (tested on Intel Core i7-5930K 3.5GHz, Win7). Disabled profiler will not affect your application execution in any way. You can leave it in your Release build and enable it at run-time at any moment during the application launch to see what is happening at the moment. ...

test-tlb is a tiny C microbenchmark that explores the performance characteristics of memory access patterns with respect to the CPU’s Translation Lookaside Buffer (TLB) and caches. It walks arrays using different strides and working-set sizes so you can observe when access patterns overflow cache or TLB capacity. By timing tight loops and varying parameters, the program reveals step-changes in latency that map to cache lines, page sizes, and TLB coverage.

The Spring Petclinic is the canonical reference sample application built with Spring Boot and Thymeleaf, demonstrating best practices in building Spring-based web applications; forks also exist showcasing implementations with modern architectures like microservices, reactive stacks, and AI integrations. In its default configuration, Petclinic uses an in-memory database (H2) which gets populated at startup with data. The h2 console is exposed and it is possible to inspect the content of the database using the jdbc:h2:mem:<uuid> URL. The UUID is printed at startup to the console. One of the best parts about working on the Spring Petclinic application is that we have the opportunity to work in direct contact with many Open Source projects.

...It handles common C features such as pointers, structs, enums, arrays, and function calls, while flagging areas that need attention during the migration. Preprocessor handling and tricky macro patterns are approached pragmatically, aiming for working output over exhaustive transformation. As a proof-of-concept, it demonstrates how automated tooling can accelerate moving from legacy C to a memory-safe language without a full rewrite.

ButterKnife is an annotation-based view binding library for Android that reduces boilerplate in Activities, Fragments, and custom views. Developers replace repetitive findViewById calls with BindView fields and define UI event handlers using annotations like @OnClick, with the library generating efficient binding code at compile time. Because it relies on annotation processing, there’s no reflection at runtime, keeping startup paths lean and predictable. The generated bind/unbind lifecycle...

...The latest version supports named fields in the STL files for tagging data parsed in the Prefix Tree and anonymous functions for parsing dynamic message payloads. We now output JSON objects and I'm working on HBase integration. By outputting to JSON it also leaves open the possibility for on the fly in memory correlation between events. Read the included README before starting, it has a quick start guide and info on the constructors.

TinyJEE is a zero conf, zero maintenance embeddable platform that has the major goal make the usage of JEE as easy as working with GRAILS while following a component oriented approach with minimized dependencies and main focus on POJO and Java config

locale4j is a Java library for working with localization data. The library currently supports the TMX file format. Future versions will support XLIFF, po and resource bundles. Translations can also be stored in memory or in a database for use at runtime.

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.

libdocsis is a shared library suitable for working with DOCSIS option files. The library provides an API to encode/decode/verify DOCSIS option files from a variety of sources including file streams, character buffers, and in-memory mapped locations.

A debuging library for C++. It does dynamic memory management with malloc and looks for potentiazl problems and leaks. It can also free up all leaked memory at the end of the program. I am currently working on hooking the new and delete keywords to wor