<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Courier New";
        color:maroon;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
/* List Definitions */
@list l0
        {mso-list-id:888566272;
        mso-list-type:hybrid;
        mso-list-template-ids:1140855692 -589381406 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-start-at:0;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<ol style='margin-top:0in' start=0 type=1>
<li class=MsoNormal style='color:maroon;mso-list:l0 level1 lfo1'><font size=2
color=maroon face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>I just finished incorporating your patch. Because it’s
late, I’m going to wait until tomorrow to check it in.<o:p></o:p></span></font></li>
</ol>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>1. There are
two reasons that your memory usage is varying. First, it is true that the
memory is not freed-up from the Cut operation. The same is true of the
data between reader and the first D3. Second, if the number of processes
you have is not a power of 2, than D3 is not perfect at distributing your
data. You can have up to twice as much data on one node as the other.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>2. It does seem
strange that one would be so different than the other 12. I don’t
have a good explanation for that.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>3. I’m
guess that has to do with your MPI implementation. It looks like it forks
a couple of times. I notice that of the 3 processes, only one is
running. The other 2 may be parents that have forked and are now waiting
(perhaps as a precaution in case the MPI job crashes and needs to be shut down
cleanly).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>4. That sounds
like a glitch. Go ahead and submit a bug report.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>-Ken<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
paraview-bounces+kmorel=sandia.gov@paraview.org
[mailto:paraview-bounces+kmorel=sandia.gov@paraview.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Randall Hand<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, August 07, 2006 2:28
PM<br>
<b><span style='font-weight:bold'>To:</span></b> Paraview List<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Paraview] Even more
Questions about ParaView on a Tiled Display</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Ok, so I've got my Mullions code (still looking for any comments about
that) working on our RenderWall and I'm noticing some interesting behaviour
that i've got some questions about.<br>
<br>
In this cluster, we have 12 nodes + 1 head node, each one connected via a
GeForce 7800GTX to a 1600x1200 LCD Display. Each node has 2 single-core
Xeon processors Hyperthreaded, for an "effective" 4 cores, and 8G of
ram. All connected via Infiniband. I've loaded up 2 PVTP
datasets: <br>
a) Dataset A is a 52Million Triangle 24-part surface, RGB per
point<br>
b) Dataset B is a 67Million Triangle 12-part surface, no data per
point (Geometry only)<br>
<br>
(Both datasets were load-balanced with Paraview's D3 filter.) <br>
<br>
Now when I load them in Paraview, with a Tiled Display, they both load and I'm
able to interact with them beautifully. 119Million Triangles rendered in
1s (for a still frame). I applied a cutting plane to one of them, and
then another D3 (to balance the newly cut surface, right?), and the results are
still fabulously interactive. But a few things i've noticed: <br>
1) Even tho the results are now "load balanced" again (via the D3),
my memory usage is still fairly varying. I'm seeing numbers ranging from
1.8G to 3.8G on various nodes. Is this because the memory isn't really
freed-up from the Cut operation? <br>
2) One of my 12 nodes is basically "idle". While the other 11
nodes show runtimes of over 250minutes on the pvserver process, one node shows
less than 5. Images are visible on all 12 displays.<br>
3) On every node I have 3 processes. 4 I would understand, and 1 I had
expected. But 3? It seems one is for the Rendering & MPI work,
while the other 2 are for computations (one has the usual spinlock runtime of
250+minutes, while the others have 0.00).<br>
<br>
An example:<o:p></o:p></span></font></p>
<div style='margin-left:30.0pt'>
<p class=MsoNormal><font size=3 face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New"'>[rhand@plasma proc]$ pdsh -a top -b -n1 | grep
pvserver | sort<br>
plasma01ib: 18580 rhand 25 0 1969M 1.9G
21052 R 25.0 25.0 275:25 1 pvserver<br>
plasma01ib: 18581 rhand 25 0 1969M 1.9G
21052 S 0.0 25.0 0:00 3
pvserver<br>
plasma01ib: 18582 rhand 25 0 1969M 1.9G
21052 S 0.0 25.0 0:00 3 pvserver<br>
plasma02ib: 18367 rhand 25 0 1926M 1.9G
21052 R 25.0 24.5 275:22 1 pvserver <br>
plasma02ib: 18368 rhand 25 0 1926M 1.9G
21052 S 0.0 24.5 0:00 0
pvserver<br>
plasma02ib: 18369 rhand 25 0 1926M 1.9G
21052 S 0.0 24.5 0:00 0
pvserver<br>
plasma03ib: 18407 rhand 25 0 3268M 3.2G
21052 R 25.2 41.7 275:20 1 pvserver<br>
...(snip)...<br>
plasma11ib: 20771 rhand 25 0 1997M 1.9G
21060 S 0.0 25.4 0:00 3
pvserver<br>
plasma12ib: 18301 rhand 18 0 4161M 4.0G
21164 S 0.0 53.1 6:38 1
pvserver<br>
plasma12ib: 18302 rhand 25 0 4161M 4.0G
21164 S 0.0 53.1 0:00 1
pvserver<br>
plasma12ib: 18303 rhand 25 0 4161M 4.0G
21164 S 0.0 53.1 0:00 1
pvserver </span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br clear=all>
<br>
4) While interacting, the 2D Scalar Bar seems to resize/move down to the
display closest the origin (lower-left corner), and then return to it's desired
location when the full-res image is rendered again. Is this a glitch, or
by design? <br>
<br>
So can someone explain to me a bit of what's going on "behind the
curtain"? I've also had no luck chasing down what's going on with
the Slow Renderings &mangled options on tiled Displays (On the <b><span
style='font-weight:bold'>production</span></b> 2.4.4 release, not my customized
mullion-enabled one)<br>
-- <br>
----------------------------------------<br>
Randall Hand<br>
Visualization Scientist<br>
ERDC MSRC-ITL <o:p></o:p></span></font></p>
</div>
</div>
</body>
</html>