Looks pretty good. Can we try even larger scale?

2014-02-11 3:18 GMT-05:00 Edward J. Yoon <edwardy...@apache.org>:

> See
> https://wiki.apache.org/hama/Benchmarks#PageRank_Performance_0.7.0-SNAPSHOT_vs_0.6.3
>
>
>
> On Mon, Jan 27, 2014 at 5:09 PM, Edward J. Yoon <edwardy...@apache.org>
> wrote:
> > FYI, this result shows the improvement obtained by removing message
> > bundling overheads.
> >
> > ----
> > PageRank with 3 tasks on single machine
> > bsp.child.java.opts: -Xmx1524m
> > hama.graph.vertices.info: ListVerticesInfo
> >
> > * Input vertices: 20000 max edges per vertex: 100
> > Hama-0.6.3: 87.895 seconds
> > Hama-TRUNK: 99.689 seconds
> >
> >  * Input vertices: 40000 max edges per vertex: 200
> > Hama-0.6.3: 340.094 seconds
> > Hama-TRUNK: 420.992 seconds
> >
> >  * Input vertices: 40000 max edges per vertex: 300
> > Hama-0.6.3: 556.07 seconds
> > Hama-TRUNK: 583.098 seconds
> >
> >  * Input vertices: 40000 max edges per vertex: 400
> > Hama-0.6.3: 733.408 seconds
> > Hama-TRUNK: 739.116 seconds
> >
> >  * Input vertices: 40000 max edges per vertex: 500
> > Hama-0.6.3: java.lang.OutOfMemoryError: Java heap space
> > Hama-TRUNK: 1207.854 seconds
> >
> >  * Input vertices: 40000 max edges per vertex: 600
> > Hama-0.6.3: java.lang.OutOfMemoryError: Java heap space
> > Hama-TRUNK: java.lang.OutOfMemoryError: Java heap space
> > Hama-TRUNK (DiskVerticesInfo): java.lang.OutOfMemoryError: Java heap
> space
> >
> > --
> > Best Regards, Edward J. Yoon
> > @eddieyoon
>
>
>
> --
> Best Regards, Edward J. Yoon
> @eddieyoon
>



-- 
------
Yexi Jiang,
ECS 251,  yjian...@cs.fiu.edu
School of Computer and Information Science,
Florida International University
Homepage: http://users.cis.fiu.edu/~yjian004/

Reply via email to