Version: v1.1.x (Second optimization run)
PC Codename: Supreme
CPU: Ryzen 5950x
RAM: 64GBs of DDR4-3200
GPU: RTX 3090ti
128x128 < 7 Seconds, ~14% improvement over First Optimization Run (0.9.x-v1.0.x).
256x256 < 16 Seconds, ~231% improvement over First Optimization Run (0.9.x-v1.0.x).
384x384 < 31 Seconds, ~677% improvement over First Optimization Run (0.9.x-v1.0.x).
All times taken from fresh game launch with external android stopwatch for minimal game impact, on a Ryzen 5950x at 4.4Ghz (allcore). YMMV.
PC Codename: Spud
CPU: i3-6100U @2.30 Ghz
4GBs of ram.
GPU: Potato.
This PC struggles far more to load the map than to generate it. Generation takes less than half the load time. Times are complete however (generation + loading, menu click to map).
128x128: < 56 Seconds, No Improvement, likely within margin of error and likely loadtime bound on this potato PC.
256x256: < 3 Minutes 17 Seconds, ~14% improvement. Again the limited ram of Potato PC is probably holding us back, but at least some gains.
384x384: Not attempted anymore with these specs. 4GB of ram would just die, pretty sure.
All times measured externally by android stopwatch to minimize impact on potato computer.
Historical results follow:
Version: v0.9.2/v0.9.3/v0.9.4/v0.10.0/v1.0.x (First Optimization Run. v0.9.1 was a bugged release with no Entity spawns, not benched. v0.9.2/v0.9.3/v0.9.4/v0.10.0/v1.0.x updates should perform equally (same core code), so also not benched.)
PC Codename: Supreme
CPU: Ryzen 5950x
RAM: 64GBs of DDR4-3200
GPU: RTX 3090ti
128x128 < 8 Seconds, ~125% improvement over initial v0.9.0 release.
256x256 < 53 Seconds, ~75% improvement over initial v0.9.0 release.
384x384 < 4 Minutes, 1 Second ~35% improvement over v0.9.0 release.
All times taken from fresh game launch with external android stopwatch for minimal game impact, on a Ryzen 5950x at 4.4Ghz (allcore). YMMV.
PC Codename: Spud
CPU: i3-6100U @2.30 Ghz
4GBs of ram.
GPU: Potato.
This PC struggles far more to load the map than to generate it. Generation takes less than half the load time. Times are complete however (generation + loading, menu click to map).
128x128: < 50 Seconds, ~74% improvement over initial v0.9.0 release.
256x256: < 3 Minutes 44 Seconds, ~50% improvement over initial v0.9.0 release.
384x384: Not attempted anymore with these specs. 4GB of ram would just die, pretty sure.
All times measured externally by android stopwatch to minimize impact on potato computer.
Version: v0.9.0 (Initial Release)
PC Codename: Supreme
CPU: Ryzen 5950x
RAM: 64GBs of DDR4-3200
GPU: RTX 3090ti
128x128 < 18 Seconds
256x256 < 1 Minute 33 Seconds
384x384 < 5 Minutes 25 Seconds
All times taken from fresh game launch with windows stopwatch, on a Ryzen 5950x at 4.4Ghz (allcore). YMMV.
PC Codename: Spud
CPU: i3-6100U @2.30 Ghz
4GBs of ram.
GPU: Potato.
This PC struggles far more to load the map than to generate it. Generation takes less than half the load time. Times are complete however (generation + loading, menu click to map).
128x128: < 1 Minute 27 Seconds
256x256: < 5 Minute 36 Seconds
384x384: Crash at < 12 Minute 29 Seconds. Generation succesful, the file is present on the computer and loadable on another one, but the game could not load it on such a potato. Logs indicate it ran out of memory.
All times measured externally by android stopwatch to minimize impact on potato computer.