Hi!
> > I'm working a project a work that is using Linux to run some very
> > math-intensive calculations. One of the things we do is use the 1-minute
> > loadavg to determine how busy the machine is and can we fire off another
> > program to do more calculations.However, there's a problem
hi,
As you've suggested, you'd be better off not using the load
average but rather some other measure (or combination of
measures) to figure out when you have enough spare cycles or
bandwidth.
The "pmie" tool might be useful to you - here's a contrived
example I just knocked up (instead of a "pr
Sorry, I know this is a little left-field, but how about redesigning your
process so that instead of using a load_avg, you start all your calculations
from a single server on each node? It could queue up incoming calculations,
and fork a child to do each one.
Of course, it would catch a signal w
> The other option we looked at, besides using loadavg, was using idle pct%,
> but if I read the source for top right, involves reading the entire
> process table to calculate clock ticks used and then figuring out how many
> weren't used.
The old "top" code did that; it was a bug. Get some newer
On Sun, Nov 05, 2000 at 07:55:40AM -0500, [EMAIL PROTECTED] wrote:
>
> We'd like to reduce that almost 50 second lag time. Is it possible, in
> user-space, to duplicate the loadavg calculation period, say to a 15
> second load average, using the information in /proc?
You could simply recompile
On Sun, Nov 05, 2000 at 07:55:40AM -0500, [EMAIL PROTECTED] wrote:
> The other option we looked at, besides using loadavg, was using idle pct%,
> but if I read the source for top right, involves reading the entire
> process table to calculate clock ticks used and then figuring out how many
> were
6 matches
Mail list logo
