Justin, I'm not sure my program counts as sufficiently simple for this purpose. I'd be happy to let you include it and get an example set up though if you want to use it anyway. The open mp part, which I haven't been using recently, may need a bit of debugging as well<div>
<br></div><div>Glen<br><div><br><div class="gmail_quote">On Mon, Oct 17, 2011 at 12:23 PM, Justin M Wozniak <span dir="ltr"><<a href="mailto:wozniak@mcs.anl.gov">wozniak@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Glen, do you have an extremely simple but relevant OpenMP program that we could stick in the test suite?<div><div></div><div class="h5"><br>
<br>
On Sun, 16 Oct 2011, Glen Hocky wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It's in my run script that creates the actual sites file that I run with.<br>
I'm not sure what you would do if you wanted more than 24 cores, so depth<br>
stays fixed at 24 (that's an aprun parameters). Then<br>
<br>
WORKERSPERNODE=$((24/$PPN))<br>
<br>
Where PPN is how many cores you want per OPENMP app and then workers per<br>
node says how many OPENMP apps you want to run. So obvious example would be<br>
you want 3 8 core OPENMP jobs, PPN = 8, WORKERSPERNODE=3<br>
<br>
<br>
On Sun, Oct 16, 2011 at 12:27 PM, Michael Wilde <<a href="mailto:wilde@mcs.anl.gov" target="_blank">wilde@mcs.anl.gov</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks, Glen!<br>
<br>
Justin, can you check the sites file below? I dont understand the<br>
interaction between the parameters OMP_NUM_THREDS, jobsPerNode, and depth.<br>
WHere is the best documentation on that?<br>
<br>
Thanks,<br>
<br>
- Mike<br>
<br>
<br>
----- Original Message -----<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
From: "Glen Hocky" <<a href="mailto:hockyg@uchicago.edu" target="_blank">hockyg@uchicago.edu</a>><br>
To: "Michael Wilde" <<a href="mailto:wilde@mcs.anl.gov" target="_blank">wilde@mcs.anl.gov</a>><br>
Cc: "David Kelly" <<a href="mailto:davidk@ci.uchicago.edu" target="_blank">davidk@ci.uchicago.edu</a>>, "ketan" <<br>
</blockquote>
<a href="mailto:ketancmaheshwari@gmail.com" target="_blank">ketancmaheshwari@gmail.com</a>><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sent: Sunday, October 16, 2011 11:18:33 AM<br>
Subject: Re: [Swift-devel] Where is latest doc on running Swift on<br>
</blockquote>
Beagle? Covers OpenMP apps?<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, I'm running and yes I did test openmp a while back. Sites file<br>
follows. I'm using trunk from a few months ago<br>
<br>
"Swift svn swift-r4813 (swift modified locally) cog-r3175"<br>
<br>
<br>
<br>
<pool handle="pbs-beagle-coasters"><br>
<execution provider="coaster" jobmanager="local:pbs" url="none"/><br>
<filesystem provider="local"/><br>
<profile namespace="globus"<br>
key="providerAttributes">pbs.<u></u>aprun;pbs.mpp;depth=24</<u></u>profile><br>
<profile key="jobsPerNode" namespace="globus">24</<u></u>profile><br>
<br>
<br>
<profile namespace="env" key="OMP_NUM_THREADS">$PPN</<u></u>profile><br>
<profile namespace="globus" key="maxwalltime">$TIME</<u></u>profile><br>
<profile namespace="globus" key="maxTime">$MAXTIME</<u></u>profile><br>
<profile namespace="globus" key="slots">$nodes</profile><br>
<profile namespace="globus" key="nodeGranularity">1</<u></u>profile><br>
<profile namespace="globus" key="maxNodes">1</profile><br>
<profile namespace="globus" key="lowOverAllocation">100</<u></u>profile><br>
<profile namespace="globus" key="highOverAllocation">100</<u></u>profile><br>
<profile namespace="karajan" key="jobThrottle">200.00</<u></u>profile><br>
<profile namespace="karajan" key="initialScore">10000</<u></u>profile><br>
<br>
<br>
<workdirectory >$swiftrundir/swiftwork</<u></u>workdirectory><br>
</pool><br>
<br>
<br>
<br>
On Sun, Oct 16, 2011 at 12:15 PM, Michael Wilde < <a href="mailto:wilde@mcs.anl.gov" target="_blank">wilde@mcs.anl.gov</a> ><br>
wrote:<br>
<br>
<br>
David, Ketan,<br>
<br>
I need to run some things on Beagle, asap.<br>
<br>
Ketan, where is the latest and best documentation for this? I see your<br>
edits below to the 0.93 Site Guide. But I dont see that online where I<br>
would expect it:<br>
<br>
<br>
</blockquote>
<a href="http://www.ci.uchicago.edu/swift/wwwdev/guides/release-0.93/siteguide/siteguide.html#_beagle" target="_blank">http://www.ci.uchicago.edu/<u></u>swift/wwwdev/guides/release-0.<u></u>93/siteguide/siteguide.html#_<u></u>beagle</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
David, is it just that this document is not being correctly pushed to<br>
the wwwdev site on a nightly basis?<br>
<br>
Ketan, is the latest info on running Swift on Beagle now all in the<br>
siteguide? Is the info you were putting in the cookbook (I see many<br>
commits there) now all consolidated into the Site Guide? And is there<br>
a difference in sites.xml settings between 0.93 and trunk? Lastly,<br>
which release works best?<br>
<br>
Second question: I need to run a script that executes many 24-core<br>
OpenMP apps. Is the necessary support for this in 0.93? What if any<br>
declarations do I need other than to say jobsPerNode=1? Glen, are you<br>
running OpenMP on Beagle and if so what release and sites file are you<br>
using?<br>
<br>
Im assuming Justin's latest changes to sites.xml are in trunk but not<br>
0.93? If that is correct, is there a corresponding site site for<br>
Beagle for trunk?<br>
<br>
Thanks,<br>
<br>
- Mike<br>
<br>
<br>
----- Forwarded Message -----<br>
From: <a href="mailto:ketan@ci.uchicago.edu" target="_blank">ketan@ci.uchicago.edu</a><br>
To: <a href="mailto:swift-commit@ci.uchicago.edu" target="_blank">swift-commit@ci.uchicago.edu</a><br>
Sent: Sunday, September 18, 2011 10:14:10 PM<br>
Subject: [Swift-commit] r5126 - branches/release-0.93/docs/<u></u>siteguide<br>
<br>
Author: ketan<br>
Date: 2011-09-18 22:14:10 -0500 (Sun, 18 Sep 2011)<br>
New Revision: 5126<br>
<br>
Modified:<br>
branches/release-0.93/docs/<u></u>siteguide/beagle<br>
Log:<br>
added content to beagle siteguide<br>
<br>
Modified: branches/release-0.93/docs/<u></u>siteguide/beagle<br>
==============================<u></u>==============================<u></u>=======<br>
--- branches/release-0.93/docs/<u></u>siteguide/beagle 2011-09-19 02:41:02<br>
UTC (rev 5125)<br>
+++ branches/release-0.93/docs/<u></u>siteguide/beagle 2011-09-19 03:14:10<br>
UTC (rev 5126)<br>
@@ -52,9 +52,38 @@<br>
A key factor in scaling up Swift runs on Beagle is to setup the<br>
sites.xml parameters.<br>
The following sites.xml parameters must be set to scale that is<br>
intended for a large run:<br>
<br>
- * walltime: The expected walltime for completion of your run. This<br>
parameter is accepted in seconds.<br>
- * slots: Number of qsub jobs needs to be submitted by swift. This<br>
number will determine how many qsubs swift will submit for your run.<br>
Typical values range between 40 and 80 for large runs.<br>
- * nodegranularity: Determines the number of nodes per job. Total<br>
nodes will thus be slots times nodegranularity. This may vary for<br>
advanced configurations though.<br>
- * maxnodes: Determines the maximum number of nodes a job must pack<br>
into its qsub. This parameter determines the largest single job that<br>
your run will submit.<br>
+ * *maxTime* : The expected walltime for completion of your run. This<br>
parameter is accepted in seconds.<br>
+ * *slots* : Number of qsub jobs needs to be submitted by swift. This<br>
number will determine how many qsubs swift will submit for your run.<br>
Typical values range between 40 and 80 for large runs.<br>
+ * *nodeGranularity* : Determines the number of nodes per job. Total<br>
nodes will thus be slots times nodegranularity. This may vary for<br>
advanced configurations though.<br>
+ * *maxNodes* : Determines the maximum number of nodes a job must<br>
pack into its qsub. This parameter determines the largest single job<br>
that your run will submit.<br>
+ * *jobThrottle* : A factor that determines the number of tasks<br>
dispatched simultaneously. The intended number of simultaneous tasks<br>
must match the number of cores targeted. The number of tasks is<br>
calculated from the jobThrottle factor is as follows:<br>
<br>
+----<br>
+Number of Tasks = (JobThrottle x 100) + 1<br>
+----<br>
<br>
+Following is an example sites.xml for a 50 slots run with each slot<br>
occupying 4 nodes (thus, a 200 node run):<br>
+<br>
+-----<br>
+<config><br>
+ <pool handle="pbs"><br>
+ <execution provider="coaster" jobmanager="local:pbs"/><br>
+ <profile namespace="globus" key="project">CI-CCR000013</<u></u>profile><br>
+<br>
+ <profile namespace="globus" key="ppn">24:cray:pack</<u></u>profile><br>
+<br>
+ <profile namespace="globus" key="jobsPerNode">24</profile><br>
+ <profile namespace="globus" key="maxTime">50000</profile><br>
+ <profile namespace="globus" key="slots">50</profile><br>
+ <profile namespace="globus" key="nodeGranularity">4</<u></u>profile><br>
+ <profile namespace="globus" key="maxNodes">4</profile><br>
+<br>
+ <profile namespace="karajan" key="jobThrottle">48.00</<u></u>profile><br>
+ <profile namespace="karajan" key="initialScore">10000</<u></u>profile><br>
+<br>
+ <filesystem provider="local"/><br>
+ <workdirectory >/lustre/beagle/ketan/swift.<u></u>workdir</workdirectory><br>
+ </pool><br>
+</config><br>
+-----<br>
+<br>
<br>
______________________________<u></u>_________________<br>
Swift-commit mailing list<br>
<a href="mailto:Swift-commit@ci.uchicago.edu" target="_blank">Swift-commit@ci.uchicago.edu</a><br>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-commit" target="_blank">https://lists.ci.uchicago.edu/<u></u>cgi-bin/mailman/listinfo/<u></u>swift-commit</a><br>
<br>
--<br>
Michael Wilde<br>
Computation Institute, University of Chicago<br>
Mathematics and Computer Science Division<br>
Argonne National Laboratory<br>
<br>
______________________________<u></u>_________________<br>
Swift-devel mailing list<br>
<a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a><br>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" target="_blank">https://lists.ci.uchicago.edu/<u></u>cgi-bin/mailman/listinfo/<u></u>swift-devel</a><br>
</blockquote>
<br>
--<br>
Michael Wilde<br>
Computation Institute, University of Chicago<br>
Mathematics and Computer Science Division<br>
Argonne National Laboratory<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br></div></div><font color="#888888">
-- <br>
Justin M Wozniak<br>
</font></blockquote></div><br></div></div>