Changes between Version 27 and Version 28 of UsersGuide

Timestamp:

Oct 25, 2012 10:33:55 AM (12 years ago)

Author:

Ted Faber

Comment:

--

UsersGuide

@@ -470 +470 @@
 which has symmetric partitions.
 
+Sometimes it is more intuitive to think in terms of the number of machines that will be used to hold containers.  The {{{--size}}} and {{{-pass-size}}} options let users express that.  The {{{--size=}}}''expsize'' option uses ''expsize'' machines to hold the whole experiment.  If multiple passes are made, each is put into ''expsize'' physical machines.  The {{{--size}}} option takes precedence over {{{--packing}}}.
+
+Per-pass sizing can be done using {{{--pass-size}}} which uses the same syntax as {{{--pass-pack}}}.  So:
+
+{{{
+users:~$ /share/containers/containerize.py --pass-size 0:1,1:1,2:2,3:4 DeterTest example6 ~/example6.tcl 
+Containerized experiment DeterTest/example6 successfully created!
+Access it via http://www.isi.deterlab.net//showexp.php3?pid=DeterTest&eid=example6
+}}}
+
+packs pass 0 into 1 physical machine, pass 1 into 1 physical machine, pass 2 into 2 physical machines and pass 3 into 4 physcial machines.  The result looks like:
+
+[[Image(example6.2-smaller.png)]]
+
+Partitions have different numbers of containers in them because metis is considering network constraints as well.  As with using packing, adding {{{--nodes-only}}} restores symmetry:
+
+[[Image(example6.3-smaller.png)]]
+
+
 The {{{--pass-pack}}} option is a per-pass generalization of the {{{--packing}}} option.  The options that can be specified per-pass are:
 
 || __Single-pass__ || __Per-Pass__ || __Per-Pass Format__ || __Per-Pass Example__ ||
 || {{{--packing}}} || {{{--pass-pack}}} || ''pass'':''packing''  (comma-separated) || --pass-pack 0:1,1:20,2:11,3:6 ||
+|| {{{--size}}} || {{{--pass-size}}} || ''pass'':''size''  (comma-separated) || --pass-size 0:1,1:1,2:2,3:4 ||
 || {{{--pnode-types}}} || {{{--pass-pnodes}}} || ''pass'':''pnode''[,''pnode''...] (semicolon separated) || --pass-pnodes 0:MicroCloud;1:bpc2133,pc2133 ||
 || {{{--nodes-only}}} || {{{--pass-nodes-only}}} || ''pass'' (comma-separated) || --pass-nodes-only 1,3,5 ||
@@ -481 +501 @@
 {{{
 users:~$ /share/containers/containerize.py --packing 5 --pass-pack 0:1,1:20 DeterTest example6 ~/example6.tcl 
+Containerized experiment DeterTest/example6 successfully created!
+Access it via http://www.isi.deterlab.net//showexp.php3?pid=DeterTest&eid=example6
 }}}
 
@@ -489 +511 @@
 {{{
 users:~$ /share/containers/containerize.py --pass-pack 0:1,1:20,2:10,3:5 --pass-pnodes '0:pc2133,bpc2133;1:MicroCloud' DeterTest example6 ~/example6.tcl 
+Containerized experiment DeterTest/example6 successfully created!
+Access it via http://www.isi.deterlab.net//showexp.php3?pid=DeterTest&eid=example6
 }}}
 
@@ -499 +523 @@
 That formulation avoids the quotes by avoiding the semicolon.  All the per-pass options may be specified multiple times on the command line.
 
+One can mix and match sizes and packing factors.  This invocation:
+
+{{{
+/share/containers/containerize.py --pass-size 1:10 --pass-pack 2:5,3:10 DeterTest example6 ~/example6.tcl
+Containerized experiment DeterTest/example6 successfully created!
+Access it via http://www.isi.deterlab.net//showexp.php3?pid=DeterTest&eid=example6
+}}}
+
+Produces:
+
+[[Image(exanple6.4-smaller.png)]]
+
 These per-pass variables and user-specified pass specifications give users fine grained control over the paritioning process, even if they do not want to do the partitioning themselves.