Re: [Condor-users] Getting cpuinfo in standard universe jobs

[Ka-Hei Law <condor-users@xxxxxxxxxxxxxx>]

Hi Tim,

Thank you very much for your suggestion.

My purpose is to record to amount of CPU power required for each run
(which varies greatly depending on the parameter). I found that the
condor internal benchmarks are very inaccurate. For example, on two
workstations with exactly the same CPU architecture, the one with a
higher clock speed consistently give a lower KFlops rating. The Mips
rating appears to make more sense, but the actual CPU speed correlates
the best with the run time (inversely).

I have no direct access to the nodes in the pools that my jobs can
flock to, and so I haven't been able to check their CPU models. I
believe hwloc will be a great addition to condor (as well as a
solution to this problem). But for the time being, I'll experiment
with CPUID first (unless someone tell me a better approach, or that
CPUID it's not going to work).

Cheers,
Ka-Hei


On Fri, Aug 12, 2011 at 11:02 AM, Timothy St. Clair <tstclair@xxxxxxxxxx> wrote:
> There is not detailed information in the SlotAd until it is
> checkpointed, even then it is limited.
>
> If you're looking for matching requirements, there are benchmarks which
> you can use:
>
> Mips
> KFlops
>
> To see the slog of information presented by your slots you can type:
>
> condor_status -long <- gives you everything
> condor_status -long slotXYZ <- gives you detailed info about a slot.
>
> If your request goes beyond *this you may want to append to:
> https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2343
>
> Hope this helps,
> Tim
>
> On Thu, 2011-08-11 at 15:13 -0400, Ka-Hei Law wrote:
>> Dear all,
>>
>> How can I get the CPU information (model and speed) on the nodes where
>> my standard universe jobs are executed? They are x86-64 Linux nodes.
>>
>> I tried reading "/proc/cpuinfo" using stdio functions in C, but the
>> "file" seems to be empty for standard universe jobs. Perhaps reading
>> the proc fs isn't supported in the standard universe.
>>
>> I found that the CPUID opcode (http://en.wikipedia.org/wiki/CPUID) may
>> give me what I need. Do you think it will work in my case? If yes, do
>> you think it's the way to go? Or would you suggest other alternatives?
>>
>> Thanks,
>> Ka-Hei Law
>> _______________________________________________
>> Condor-users mailing list
>> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>>
>> The archives can be found at:
>> https://lists.cs.wisc.edu/archive/condor-users/
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>