Code Monkey home page Code Monkey logo

stress-1.0.4's Introduction

INSTALL

See the INSTALL file for generic installation instructions. The quick version is:

./configure && make && sudo make install

USAGE

You can see the program's usage statement by invoking it with --help. A typical invocation is:

stress --cpu 8 --io 4 --vm 2 --vm-bytes 128M --timeout 10s

A user manual is available:

info stress

The project home page is:

http://web.archive.org/web/20130520190152/http://weather.ou.edu/%7Eapw/projects/stress/

PATCHES

This program worked really well for the original author (Amos Waterland), but it might not have some of the features that you want. If you would like, please extend the code and send Amos the patch. Please use the context diff format. That is: save the original program as stress.c.orig, then make and test your desired changes to stress.c, then run diff -u stress.c.orig stress.c to produce a context diff. Alternatively, you could try sending a pull request on GitHub, although please note that if you are viewing this in repository form on GitHub, you are viewing a fork by a random user with no connection to the original project. In any case, enjoy the program! :-D

Amos Waterland [email protected] Norman, Oklahoma 27 Nov 2001

stress-1.0.4's People

Contributors

cooljeanius avatar dependabot[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

stress-1.0.4's Issues

`stress --hdd` to stop at end of `--timeout` period

Copying from my Stack Overflow question:

I am using stress --hdd 1 --timeout 10s -v to stress the IO/disk on an Ubuntu system. Sometimes when running this command, I get something like:

stress: info: [16420] dispatching hogs: 0 cpu, 0 io, 0 vm, 1 hdd
...
stress: info: [16420] successful run completed in 13s

and other times I got something like:

...
stress: info: [16390] successful run completed in 31s

With iostat -yx 1 open in a separate terminal, I can indeed see that the %util and aqu-sz size stay high for roughly that longer-than-specified amount of time. I also see the mmcqd/0 process at the top of top.

How can I get the IO stress to stop within +2 seconds of the --timeout argument given in the stress command?

I have tried stuff like timeout 10 stress --hdd 1 --timeout 10s -v; pkill stress; pkill mmcqd;
without much success. Is there a way to purge the IO queue?

Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.