Closed GoogleCodeExporter closed 8 years ago
Ok, reviewed and fixed the problem.
The provided parse covered a 2 month period, for 5.5 million seconds. The
program
was creating arrays for the damage for all of the players for all of those
seconds,
requiring (at best) 8 * 8 * 5.5m * 2 = 700MB of RAM. There's a possibility of
needing twice that, but I didn't do a full check on that.
It should now take no more than ~50 MB for the same dataset. The time scale
shown,
though, will be increased and fixed. The sample parse, for example, requires
an x16
scale. As such, all data points on the graph will be in 16 second intervals
rather
than 1 second intervals.
Original comment by Kinemati...@gmail.com
on 2 May 2010 at 3:50
Original issue reported on code.google.com by
raphael.morineau@gmail.com
on 1 May 2010 at 12:42Attachments: