I'm not surprised about this problem, as I have same issues with large graphs like this. This is due to our current implementation of our GEXF parser, which basically eats a lot of memory (we use DOM...). Hopefully I started a new GEXF parser, using STAX which is keeping a very low memory footprint. I will continue the work on this parser as soon as possible (if someone wants to help me...feel free) and include it in the next release.
I'm not sure if it will make it, but you can try to use a 64-bit JVM and increase memory up to 4GB.Statistics:Posted by mbastian — 06 Jun 2010 15:32
]]>