Free workplace stress software for linux

StressLinux is a minimal linux distribution running from a bootable cdrom (LiveCD) or via PXE.
stresslinux makes use of some utitlities available on the net like: stress, cpuburn, hddtemp, lm_sensors ...
stresslinux is dedicated to users who want to test their system(s) entirely on high load and monitoring the health.
Main features:
- stress 0.18.1 (A tool to impose certain types of stress on a POSIX system.)
- CPUBurn 1.4 (CPU maximum load (heat) stability test)
- CPU Burn-In 1.00 (CPU burn-in test)
- nbench 2.2.1 (CPU test suite)
- iometer 2003.12.16 (I/O performance meter)
- hddtemp 0.3beta11 (A program to display the temperature of your hard drive.)
- lm_sensors 2.8.7 (LM78 and other hardware monitor drivers.)
- busybox 1.0.0rc3 (Single small executable which contains common UNIX utilities)
- lshw A.01.07 (Hardware lister)
- bonnie++ 1.03a (Hard drive benchmark)
- netio 1.23 (Network benchmark)
- smartmontools 5.32 (S.M.A.R.T. drivetests)
- x86info 1.12b (CPU information)
- memtest86 3.1a (A stand-alone memory diagnostic)
- memtest86+ 1.15 (An other stand-alone memory diagnostic)
Enhancements:
- This release updates the kernel to 2.6.16.18 and busybox to 1.1.3, adds the network test tools netperf, iperf, and nepim, and adds an extra option to boot without loading extra drivers from initrd.

KDE Menu Sidebar Image Improvement is a simple improvement for your KDE Menu that replaces default KDE Menu Sidebar image with one designed specifically for your Slackware GNULinux distribution.
Having say a Slackware or Debian or FreeBSD or any other OS/distribution logo instead of default KDE gear may be a much better choice for those of you who are just in love with your favorite *nix.
Personalized it looks sexy, it looks witty, it stresses the facts.
This project proved to be a little success because people seem to appreciate it.
So, now here we are with updated package again and it is my pleasure to hear from you that youve given it a try.
Enhancements:
- Project structure has been redefined so that it is now template based and extensible. This is basically a first attempt to unify all types of KMSBII presented at kde-look.org.
- Installation script has been dramastically improved; added new features to control the installation process and the ability to perform post-installation actions; run `./install.sh help for more information. The script is quite verbose now and informs user of every action performed in a user-friendly manner;
- Abbreviations of the project related names have been introduced to provide a convenient way to refer to them. See "ABBREVIATIONS" section of `./install.sh help output;
- Graphic source files as well as KMSBI files have been changed once again, changes have been made to achieve the best look of the KMSBI;
- Added KMSBII for Slackware GNULinux distribution v11.0.0;
- Updated documentation.
- Licensing agreement has been introduced to protect intellectual property and rights of its owner. See COPYING file for more details and "Licensing Agreement" section of this file for short explanations on how this licensing agreement works.

OSCache is a high performance J2EE caching solution that can cache portions of JSP pages, entire HTTP responses (including dynamically generated images), and arbitrary Java objects.
OpenSymphony Cache can provide your J2EE application with huge performance gains and graceful error tolerance (e.g., in the event of a DB failure, cached content is served).
Fast in-memory caching
OSCache allows you to execute dynamic content periodically (eg every 30 minutes) rather than every request and store the result in memory. Each further request is served directly from the memory cache, resulting in dramatic speed increases.
The cache is keyed programmatically. This means you can calculate a cache key that works for your situation. For example an ecommerce site might use product ID as keys, or content site might use an article date and article ID combination.
The cache is stored in standard scopes that any JSP programmer is familiar with (application or session). The session scope allows you to have different cached content per user. This is one unlike any other caching system weve ever seen.
Persistent on-disk caching
OSCache can also write the cache to disk. This provides caching across server restarts, and caching of datasets that do not fit into memory. Caching can be configured to use memory or file caching, or a combination of both.
If you want to persist the cache to somewhere other than disk, you can plug in a custom PersistenceListener. This allows you to persist the cache to anywhere (for example to a database via JDBC or to LDAP via JNDI).
When using both disk caching and memory caching. It is possible to limit the cache size to avoid using too much memory but let disk cache unlimited, resulting in browser style complementary disk cache. When cached objects are removed from memory, they are still on disk. If the item is needed again and it is not expired the cache file will be used. This also gives fault tolerance if the server crashes.
Persistence can also be switched to overflow mode using the property oscache.persistence.overflow.only. This changes the default behavior (of persisting every cache entry when there is a listener) to only persist when the memory cache capacity has been reached.
Excellent Performance
Written with performance in mind.
Mulitple cache requests can be handled concurrently.
Only one requesting thread needs to update an expired cache entry even if multiple threads are requesting it simultaneously. Other threads can be configured to either receive the recently-expired object, or block until the cached object is updated. Similarly, when a new entry is being added to the cache, other threads requesting that entry will block until it is ready rather than run off and race to build the same object. In a high load environment this can provide enormous performance benefits.
Automatically takes advantage of JRE 1.4 or higher if available.
Clustering support
OSCache can easily be configured to cluster across multiple boxes. This provides both scalability and failover support without any changes required in your caching code.
Flexible Caching System
OSCache allows you to cache portions of JSP pages, arbitrary Java objects, and even entire servlet responses.
Cache capacity can be set allowing you to limit the number of cached objects.
Multiple caching algorithms are supported such as LRU (Least Recently Used), FIFO (First In First Out), or unlimited. It is also possible to plug in your own custom algorithm.
You are given a huge amount of control over the way cached objects expire. Objects can be cached indefinitely, expired once they reach a certain age, or expired based on a cron expression. Programmatic flushing is also possible, and if that is still not enough pluggable RefreshPolicies allow custom refresh strategies.
Cached objects can be grouped together however you like, allowing for powerful management of cached data. This is an extremely useful feature that is far more powerful than what other caching solutions typically offer (such as the flushing of cache keys that match a particular pattern).
Fully event driven! OSCache fires events for various happenings under the hood such as cache entry events (adding, updating, flushing and removing) and cache accesses (hit, stale hit and miss). It is easy to add your own event handlers.
Multiple caches can be created, each with their own unique configuration.
Simple JSP Tag Library
The tag library to perform and control the caching is very simple. See the Tag Reference for more information.
Caching Filter
A Servlet 2.3 Filter allows for caching of entire pages and generated binary files (like dynamically created images or PDF files).
Comprehensive API
For the ultimate control, OSCache can be used through its straightforward API. You can instantiate, configure and control multiple caches programmatically. It would be possible for example to create one small in-memory cache that held currency conversion rates and was updated daily at 2am, while another cache could be purely disk based and used for holding dynamically created images.
Exception Handling
OSCache provides a way for your site to gracefully tolerate errors. This is not error prevention, rather if an error occurs it should not stop your site from functioning. For example if your database goes down, normally your product descriptions will not be browsable. Using OSCache you can cache those descriptions so you can still browse them.
Cache Flushing
Flushing of caches can be controlled via JSP Tags, so these functions can easily be built into your administration interface.
There is programmatic control over what caches are flushed (eg all caches or just a particular scope).
Cached objects can be expired in a number of ways. Objects can be told to expire once they reach a certain age, or, through the use of cron expressions, on particular dates and/or times (eg it is trivial to make an object expire every weekday at 3am). If this is not enough, you can expire objects programmatically as required, or plug in your own custom RefreshPolicy class that can dynamically decide when an object should be flushed.
Entire groups of objects can be easily flushed from the cache. For example suppose you were caching product data as well as entire pages of your website. When a product was updated, you could flush not just the product object but also all the pages that contain information about that product. No more waiting for the cached objects to expire before the updated content shows up on your site!
Portable caching
Pure Java, this means it is platform independent.
OSCache is compliant with Servlet 2.3 and JSP 1.2 standards, which means it should work in the latest generation of servlet containers and application servers.
i18n Aware
The caching is i18n aware and supports all encodings.
Solid Reputation
Thousands of downloads, hundreds of users on the mailing list.
Comprehensive JUnit test suite that covers every aspect of OSCache, including a web stress test and various concurrent cache access scenarios. To back this up, the kind folks at Cortex have supplied us with a Clover license to provide detailed code coverage analysis of our unit tests.
We have solid issue tracking using JIRA to keep track of any feature requests, bug reports and development progress. JIRA is provided courtesy of Atlassian.
Enhancements:
- CRON expressions to expire content at specific dates and/or times.
- Pluggable EntryRefreshPolicy.
- Reduced memory consumption.
- Faster disk persistence.
- DiskPersistenceListener deadlocks are avoided if a process has no rights to delete the cache file.
- There is a new JSP tag _addgroups_, and an interface to get a list of the cache event listeners.
- The commons collection dependency has been removed.
- Java 1.3 support has been dropped.

Bugnux is a complete Linux (mandriva) distribution that runs from a single bootable CD and runs entirely in RAM. Bugnux contains an extensive set of Open Source software testing tools that can be used for functional and performance testing.

Standalone Tools to test GUI applications and Mozilla Firefox extensions pre-installed to aid in web application testing have been packaged. This virtually can turn any PC into black-box testing device without having to install any software. Bugnux also contains a set of stress and load testing tools that can be used to assist in testing performance of web applications.

The technique to allow bugnux to boot and run from RAM is based on a project called PCLinuxOS. PCLinuxOS is a bootable CD with a collection of GNU/Linux software, automatic hardware detection, and support for many graphics cards, sound cards, SCSI and USB devices and other peripherals. PCLinuxOS can be used as a Linux demo, educational CD, rescue system, or adapted and used as a platform for commercial software product demos. It is not necessary to install anything on a hard disk. Mastering of this CD uses on-the-fly decompression which allows for up to 2 GB of stored data.

Starting with the 1.1 version of bugnux, we have started completely from scratch by installing a basic PCLinuxOS installation then adding the software testing functionality afterwards. This allowed us to have more control and understanding of what is on the CD.

GnomeKiSS project is a KiSS paper doll viewer for GNOME.
GnomeKiSS is an implementation of French-KiSS for the GNOME desktop environment, using GNOME, GTK+ and the X Window System. French KiSS is an enhanced KiSS/GS for scriptable dolls, where KiSS is an abbreviation for Kisekae Set System (or something).
GnomeKiSS apparently works on plenty of Linux systems (including Debian GNU/Linux and PLD Linux) and is available as a FreeBSD port. If you dont have one of these Free operating systems I have been told that GnomeKiSS compiles and runs on Mac OS X and Sun Solaris too. It should work on any modern Unix-like system with GNOME installed but obviously I cant test them all.
Enhancements:
- GNOME 2.x conversion aiming at GNOME 2.6 and later
- Many new compiler warnings fixed, e.g. sign and const fixes
- Further changes to event handling to ensure interactivity when stressed
- Fixed snprintf() call to stay strictly within the buffer
- Still warn, but dont ignore objects declared after @EventHandler

FunkLoad project is a functional and load web tester, written in Python, whose main use cases are:
- Functional testing of web projects, and thus regression testing as well.
- Performance testing: by loading the web application and monitoring your servers it helps you to pinpoint bottlenecks, giving a detailed report of performance measurement.
- Load testing tool to expose bugs that do not surface in cursory testing, like volume testing or longevity testing.
- Stress testing tool to overwhelm the web application resources and test the application recoverability.
- Writing web agents by scripting any web repetitive task, like checking if a site is alive.
Main features:
- Functional test are pure Python scripts using the pyUnit framework like normal unit test. Python enable complex scenarios to handle real world applications.
- Truly emulates a web browser (single-threaded) using Richard Jones webunit:
- basic authentication support
- cookies support
- fetching css, javascript and images
- emulating a browser cache
- file upload and multipart/form-data submission
- https support
- Advanced test runner with many command-line options:
- set the target server url
- display the fetched page in real time in your browser
- debug mode
- green/red color mode
- Turn a functional test into a load test: just by invoking the bench runner you can identify scalability and performance problems.
- Detailed bench reports in ReST or HTML (and PDF via ps2pdf) containing:
- bench configuration
- tests, pages, requests stats and charts.
- 5 slowest requests
- servers cpu usage, load average, memory/swap usage and network traffic charts.
- http error summary list
- Easy test customization using a configuration file or command line options.
- Easy test creation using TestMaker / maxq recorder, so you can use your web browser and produce a FunkLoad test automatically.
- Provides web assertion helpers.
- Provides a funkload.CPSTestCase to ease Zope and Nuxeo CPS testing.
- Easy to install and use, see examples in the demo folder.
Enhancements:
- This release fixes some HTTP encoding and reporting bugs, it also brings support for Python 2.5.

GliBench is a Gui based benchmarking tool to check your computers CPU and hard disk performance. The software is based on the benchmarks I developed for CliBench Mk III SMP a SMP enabled benchmark program for Win32.
There were several tries to port it to other architectures than Win32, but this was not that easy. So I decided to to a Linux port, based on the GTK toolkit with Gnome support, as Linux runs on almost every hardware around and GTK is quite easy to port to other OSs.
The CPU tests are all ported to ANSI C. They run fully multithreaded using posix threads. You can already use the program for benchmarking your hardware.
Enhancements:
- The application was completely rewritten for GTK+ 2.x and Glib 2.x.
- New stress tests and threaded I/O tests for benchmarking hard drives are available.
- Both console and GUI interfaces are available.