fonsinchen wrote:

r26646 reduces the size of the saveload chunk but is not straightforward to backport to 1.4 as it also bumps the saveload version.
r26650 allows larger saveload chunks, of up to 4GiB

Some patches to backport r26646, reactivating the minor saveload version have been proposed. However, as r26650 can easily be backported I think that's unnecessary. With such large link graphs you already need a lot of RAM to keep the in-memory representation of the link graph around and the RAM requirements are still moderate compared to the CPU requirements of actually running such a game. On my computer the given savegame runs unplayably slow, but uses only about 500MiB to 1GiB of the 4GiB of RAM available. The save games are somewhat larger without r26646 but as the example shows they can be compressed very efficiently.

We could use a sparse vector or matrix implementation to optimize the in-memory representation of link graphs for size, but as most of the time link graphs are much smaller than the example given here I don't think it's worth it.

This comment was imported from FlySpray: https://bugs.openttd.org/task/6041#comment13384

Rubidium closed the ticket.

Reason for closing: Fixed

This comment was imported from FlySpray: https://bugs.openttd.org/task/6041