On 2009-Aug-25 19:50:04 +0100, "Dr. David Kirkby" <[email protected]> wrote: >Note I've implement the load averages in two ways: > >* System as a whole >* Processors available to Sage, which might have a very different load >average if its running in a Solaris Zone or as a virtual machine with >only a limited number of processors available.
The latter may not make sense on other operating systems. Should they
return the system-wide load average or an error?
>My intension is to add something to Sage so this sort of information can
>be found on Solaris. I'll leave it to others to get the data from linux,
>OS X etc.
I think there needs to be more co-ordination than this. The data
collected needs to be both useful and available on other platforms.
There may be cases where providing exactly the same data is
comparatively expensive on other systems and an alternate definition
would provide similar information far more cheaply.
>The following 3 commands apply to one single process of a given PID:
>./a.out image_size PID (Image size in MB)
>./a.out resident_size PID (Resident size in MB)
These either need to be a floating point value or reported in
smaller units. Typical granularity is pages.
>./a.out process_priority PID (Priority)
Is this expected to be comparable across different OSs? If so,
there needs to be agreement on what different numbers mean.
>./a.out processor_speed (CPU speed in MHz, rounded to
>the nearest integer)
Most OSs support CPU throttling (I think even Solaris does on some of
the CoolThreads boxes) and current x86 family CPUs allow diffent cores
to throttle to different speeds. Does this represent the top speed of
the fastest CPU, average top speed, current CPU speed or what? Note
that averaging current speed is probably not a good idea because a
single-threaded sage may be saturating one core (hence it is running
at full speed) whilst the other core is idling (and therefore
throttled to minimum).
>./a.out physical_processors (Number of physical CPUs)
Total CPUs or CPUs available to the Sage (via processor set or
similar). What is the definition of a CPU - put another way, how
many CPUs in a T5120? 1, 8 or 64?
>./a.out platform (SUNW,Sun-Blade-1500,
>SUNW,Sun-Fire-T200 etc)
What do you expect a PC to report here? The SMBIOS System Product?
>./a.out solaris_version (The version of Solaris (7, 8,
>9, 10, 11 etc)
For portability, this should be something neutral like 'os_version'.
Note that Sun still prefer reporting it as SunOS 5.x. Is this intended
to be a float (eg 5.10 or 2.6) or a string (eg '2.6.24-19-server')?
Once you start looking beyond Sun Solaris on SPARC, there are a variety
of other details that become relevant as well:
- Vendor (eg the SMBIOS System Maker on a PC)
- OS Name ("Linux", "Solaris", "FreeBSD" etc)
- Architecture ("SPARC", "x86", "x86_64", etc)
- Anything else I've forgotten.
- CPU type (cpuinfo model name on Linux)
--
Peter Jeremy
pgpV7PVgNSaZ5.pgp
Description: PGP signature
