Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
The classic Linux job scheduler is cron, and I know of no "simulator" for that. One sets up a "cron job" and it either works or it doesn't. If it doesn't, one troubleshoots it until it does.
Although you might be able to conduct a meaningful simulation of an operating-system scheduler, "frankly, I doubt it." There are simply too many variations in what might happen "next." (Or, the data is simply too abstract ... you gather it, but what does it mean, what does it tell you, and what can you do with it, and how can you usefully compare it to anything else?)
Often, what is done is to instrument certain applications so that they collect statistics over the space of at least several seconds by which you can infer what must be happening, generally using classical statistical analysis techniques upon the collected data-set.
A very strong approach is to set some sort of objective about which one can say that it was either "met," or "not met," and from this set a goal concerning this objective. You have now engineered a binomial test situation. An experiment. Alternatively, you can decide upon a "closeness" factor ... how close were we to meeting the goal? And, you can analyze the distribution of those.
I guess it's a bit like quantum physics, where you can never actually observe something, but you can analyze its effects.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.