In RH342 a handy little piece of code to leak memory called bigmem is used.
Is this code available outside of the education?
Per experience, while it is a good thing to learn things through our lab excercises, binaries and/or codes in a controlled environment, there are many other ways to learn just that too, yielding the same objective/s.
When you are totally on your own creating a controlled environment youself and achieving the expected results, you definitely learn more and are at a new level of confidence. <Disclaimer> IMHO </Disclaimer>
On a side note, I did stuy RH442 (Performance Tuning), ??? a deeper course of RH342 ???, years ago in a classroom with Red Hat and of course, I can google and get just about every piece of code or idea I need sorted. <NoteToSelf> The bright side of the Internet </NoteToSelf>
Likewise, for your case, see this below for your reference.
And that is what I meant by "In general, Yes".
Hope this helps.
I agree that Ravello is slow due to GUI Payload Overhead over https.
Having said that, it is one hell of an educational subscritpion that can help you learn so much of Red Hat Technologies (From RHCSA to RHCA).
I see you have two advantages when you have such a subscription:
1. It is better to have a slow lab than no lab at all
2. You can build your own environment and you can always refer to the lab at will.
There are a few limitations though when doing things from scratch:
One of which is you will need to learn a lot which may be outside of your learning objectives and they are considered a bit of distraction when you have time constraints.
Another is Red Hat's T&Cs and that is a grey area.
Have fun hacking. I am glad I am of some help around here.
Typically Red Hat does not make available the materials from within a training class. For this particular request, it falls into the category of "Why would Red Hat provide an application that will cause a failure of a system?" Essentially, while it can be handy for forcing an OOM or just locking onto a large amount of memory, if it were to be used on a production system it could wreak havoc. Imagine that happening and the culprit saying "Well I got this from Red Hat." Ugh.
Essentially this program is written in C and uses mmap, or associated calls for different allocation types, to allocate the amount of memory passed as an argument on the command line. (If I recall correctly, it's been a while since I've looked at the source or compiled it.) The last iteration of the program some command-line switches were added to allow the user to toggle to different calls for the different types of requested memory. All in all it was like a 20 line program, so if one was so inclined to do so, it shouldn't be horrible to recreate on one's own.