SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Back in my younger days when Windows was the name of my game, I had a small suite of programs to benchmark new servers, just to make certain everything was running as it was supposed to. Also some of these tests could be made to run in a loop for stresstesting over a longer period of time.
Now that I'm running nothing but Linux, I've more or less abandoned this practice. Perhaps because things just work, but perhaps also because I haven't had the time/energy/knowledge to really look into how this can be accomplished on Linux.
So my question: What do you guys use for general benchmarking and stresstesting prior to moving a server into production?
Distribution: Red Hat CentOS Ubuntu FreeBSD OpenSuSe
Posts: 252
Rep:
Quote:
Originally Posted by TL_CLD
Hey all,
Back in my younger days when Windows was the name of my game, I had a small suite of programs to benchmark new servers, just to make certain everything was running as it was supposed to. Also some of these tests could be made to run in a loop for stresstesting over a longer period of time.
Now that I'm running nothing but Linux, I've more or less abandoned this practice. Perhaps because things just work, but perhaps also because I haven't had the time/energy/knowledge to really look into how this can be accomplished on Linux.
So my question: What do you guys use for general benchmarking and stresstesting prior to moving a server into production?
Regards,
Thomas
For me I tried loops of recompiling different versions of kernel simultaneously. And run it overnight in a public network with no firewalls and almost all applications are open. you just need to have a big bandwidth in case some script kiddies hack your open system and will cause a ddos. add a script that will shutdown if it reaches your threshold limit for bandwidth utilization
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.