OSHI - Native Operating System and Hardware Information

•    Java

---

OSHI is a free JNA-based (native) Operating System and Hardware Information library for Java. It does not require the installation of any additional native libraries and aims to provide a cross-platform implementation to retrieve system information, such as OS version, processes, memory & CPU usage, disks & partitions, devices, sensors, etc.

operating-system hardware-information jna serialnumbers cpu-usage memory-usage disk-utilization process-list system-monitoring processor usb-devices hardware system-information

systemstat - Rust library for getting system information

•    Rust

---

Unlike sys-info-rs, this one is written purely in Rust. See examples/info.rs.

system uptime system-information memory-usage battery-status cpu-load boot-time loadavg load-average

systemstat - Rust library for getting system information

•    Rust

---

Unlike sys-info-rs, this one is written purely in Rust. See examples/info.rs.

system system-information uptime battery-status cpu-load memory-usage boot-time loadavg load-average

audria - audria - A Utility for Detailed Ressource Inspection of Applications

•    C++

---

audria can be used to monitor a single process, a group of processes or all currently running processes. Furthermore it is possible to specify a command to execute in order to watch a process directly from startup. In contrast to some other tools, audria is designed to run in batch mode at very short intervals. This allows very detailed inspections of the resource usage of a process.

resources analyzer statistics cpu load io throughput inspection monitor monitoring resource-measurement cpu-monitoring cpu-usage memory memory-monitoring memory-usage threads profiling profiler

log-malloc2 - Memory allocation tracking library

•    Shell

---

log-malloc2 is pre-loadable library tracking all memory allocations of a program. It produces simple text trace output, that makes it easy to find leaks and also identify their origin. There is (non-)small performance penalty related to writing to logfile. One can improve this by redirecting write to tmpfs or similar fast-write filesystem. If log-malloc2 is compiled without libunwind, additionally a synchronization mutex is used while writing to logfile, thus every memory allocation is acting as giant synchronization lock (slowed down by write to logfile).

memory-allocation backtrace leak-detection memory-leaks memory-usage

gocache - High performance and lightweight in-memory cache library with LRU and FIFO support as well as memory-usage-based-eviction

•    Go

---

gocache is an easy-to-use, high-performance, lightweight and thread-safe (goroutine-safe) in-memory key-value cache with support for LRU and FIFO eviction policies as well as expiration, bulk operations and even persistence to file. It also supports cache entry TTL, which is both active and passive. Active expiration means that if you attempt to retrieve a cache key that has already expired, it will delete it on the spot and the behavior will be as if the cache key didn't exist. As for passive expiration, there's a background task that will take care of deleting expired keys.

redis key-value cache lru redis-server inmemory in-memory kvstore expiration expire ttl fifo lru-cache memory-usage fifo-cache go-cache inmemory-cache memory-usage-based-eviction