Re: [Condor-users] Best practices for CPU architecture optimizations?

["Burnett, Ben" <ben.burnett@xxxxxxxx>]

You might consider using the "crondor" functionality to introduce new class ad attributes for each individual setting you want, rather than a string in which you have to search for substrings.

For instance, you might have:

HasSSE2=True

Or,

HasSSE=True
SSEVersion=2

Depending on how you wanted to write your expression.  Take a look at the following section of the manual to see if this is the behaviour you want:

http://www.cs.wisc.edu/condor/manual/v7.4/3_3Configuration.html#16883


-B

--
Ben Burnett
Optimization Research Group
Department of Math & Computer Science
University of Lethbridge
http://optimization.cs.uleth.ca

"Absence of evidence is not evidence of absence" 
- Carl Sagan

On 2011-01-21, at 9:48 AM, Lans Carstensen wrote:

> We're discussing how best to set up for steering jobs optimized for and/or requiring AVX extensions[1].  I'm hoping someone else has a best practices guide on expressing and then ranking or requiring CPU flags in classad's.
> 
> The approach I'm thinking of is setting a CpuFlags ClassAd to:
> 
> grep flags /proc/cpuinfo | head -1 | cut -d: -f2
> 
> ...so one could use a Rank or Requirements expression of:
> 
> stringListMember("sse2",CpuFlags," ")
> 
> ...for SSE2 jobs, for instance.  Is that what others are doing already, or is there a better practice out there from the folks that have been doing this longer?
> 
> [1] http://en.wikipedia.org/wiki/Advanced_Vector_Extensions
> _______________________________________________
> 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/