Search Results for "allocator"

jemalloc is a general purpose malloc(3) implementation that emphasizes fragmentation avoidance and scalable concurrency support. jemalloc first came into use as the FreeBSD libc allocator in 2005, and since then it has found its way into numerous applications that rely on its predictable behavior. In 2010 jemalloc development efforts broadened to include developer support features such as heap profiling and extensive monitoring/tuning hooks. Modern jemalloc releases continue to be integrated back into FreeBSD, and therefore versatility remains critical. ...

VulkanSceneGraph (VSG), is a modern, cross-platform, high-performance scene graph library built upon Vulkan graphics/compute API. The software is written in C++17 and follows the CppCoreGuidelines and FOSS Best Practices. The source code is published under the MIT License, with the exception of vulkan.h, used for Vulkan extensions, which is under Apache License 2.0. This repository contains C++ headers and source and CMake build scripts to build the libvsg library. Additional support...

...The memory model chosen is NUMA without pagination. During the initialization, the memory is divided proportionally for each processor installed on the system. When a thread needs memory, the memory allocator returns a free block of memory depending on which CPU the thread is running. In the same way, TORO can dedicate resources to specific processor, i.e. a FileSystem. This only CPU then can access to this instance of FileSystem. The scheduler is based on the cooperative threading model, therefore due to this design, TORO can migrate threads between CPUs and send messages between threads without using any lock instruction. ...

a shared memory allocator that provides a simple interface for named shared memory segments; shared memory between any processes; provides shared memory queues; does not use the same address between processes; fast structured arena file scales well

...More scalable and memory efficient than mtmalloc, ptmalloc, Hoard, etc. Allocations are very fast, with no lock contention and the least memory waste of any other allocator. Concur is optimized especially for applications that make heavy use of memory allocation in a threaded environment, or that just want to make the best use of every ounce of available memory. Just plugs right into your existing application without modification! The new 2.0 update includes a variety of new optimizations to make Concur even more memory efficient.

Fuzzy Traffic Shaper as bandwidth allocator based on connection reservation

The Steel Allocator is a memory allocator. It is principally designed to have a low theoretical bound on memory waste--memory held from the system but not actually in use by the program. Performance and security are also taken into account.