If you need real time / close to real time.. then i agree with Job.
but if you just need the proc to be done as fast as possible..
do two things. put sar on your linux box and see what the stats show
with the box doing NOTHING.. other than its basics.. Then with
that baseline.. you have an idea of what resources you have to
tell your process to use up and where you bottle necks might
be (disk, mem swap, ) Now you can deside to use the best kernel
scheduler
for you demands. and start the proc up with a nice command ..
This is a somewhat convoluted question, but here goes...
We are creating a system that has a "timeline" (e.g. tasks must
be completed in a given amount of time)
OK, so we have a processor (we'll stay generic at this point)
that will be running a linux based kernel, and we want to figure out how
much processor availability we have (e.g. clock tics in a given time).
We know that the kernel functions (including resource
allocation, interrupt hadling, and so on) take up some omount of CPU
horsepower (albeit small)
What is a good general rule of thumb for a barebones linux
system? I know this is gross estimation, but does the kernel use up 20%
of my CPU resources? 10%? Any ideas?
Thanks
Tom
and message 13
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
