On Mon, Nov 4, 2013 at 11:56 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:

>
> On Nov 4, 2013, at 12:28 PM, John Peterson <jwpeter...@gmail.com>
>  wrote:
> >
> > Nicely done yet again!  The new implementation ran faster, and cut .23
> Gb of memory.  That is a pretty huge memory savings for a 2 Gb mesh,
> especially considering the graph is only actually formed on one processor
> now.
> >
> >
> https://drive.google.com/file/d/0B9BK7pg8se_iSTZMNXFtUFZ3QTQ/edit?usp=sharing
>
> It's a good day when memory usage goes down and speed goes up at the same
> time!
>

Didn't even have to use my AK.

For completeness, here's a plot showing the history of all the
optimizations to our Metis prep (on two cores):

https://drive.google.com/file/d/0B9BK7pg8se_iVWxCTElwTUpmbXc/edit?usp=sharing

Memory savings from each optimization:
vectormap: 0.49 Gb
broadcast: 1.16 Gb
csrgraph: 0.34 Gb (previously-reported .23 Gb may have been a bad data
point, .34 Gb comes from averaging over 5 runs)
-------------------------
total: 1.995 Gb

-- 
John
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to