The stress load used is (unfortuneatly) proprietary in that the code was generated on company time.
It is a collection of tests designed to simulate several classes of time-sharing user. It is loosely based on UETP code use by VaxVMS and code generated for Tru64Unix. The components include: - A memory test - user mode read/write memory - Bourne shell exerciser - uses sed and sort for test processing - Compiler - unpacks c source code, compiles - File test - create, write, read, delete - Memory mapper - uses shared memory - Signal handler - in place of crashme There is a master script which invokes each of the sub tests in sequence until the number of requested test processes have been detached. >From experience with other platforms, values are know at which the system should run stable and where problems start to be encountered. Normally we are able to isolate a problem and then use a targetted test to isolate to a specific sequence, library etc. In the Ubuntu case we have a more fundamental problem where calls to gettimeofday(), and ps fail. We have worked around the crashme problem by not using that specific test. --------- I will try feisty next. Thanks ted -- Sparc t2000 hangs under stress load https://launchpad.net/bugs/91601 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
