Search Results for "cpu stress testing"

DBD2 inserts database records from TCP input. It is a companion project to Syslgod2 and an application in its own right. It ships with a backgrounding client for generic use. The client sends whatever information the user puts on the command-line to the back-end daemon via TCP. Upon successful transmission, the client exits. On failure, it backs off and retries until its life-time timer expires. The back-end daemon accepts data from Syslogd2 or its own client and inserts that data...

Using templated message formats with customisable placeholders, run in configurable sequences that can selectively reuse data between steps, must allows more intelligent testing of syslog receivers with realistic data, as well as longer soak testing and stress testing. must was created to fill a gap found when trying to stress test Splunk as real, indexable and meaningful data was needed. must will (eventually) be provided as a standalone tool that uses XML configs (for quick use and consultancy etc) and as a web-based tool (for more permanent/pretty deployment (with historical reporting and live stats). ...

The software program (SarBox) parses and analyzes SAR data in charts or text formats. 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...