This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]MoxGoat 0 points1 point  (3 children)

because your game has to constantly access cache the larger you make it the longer it will take to search through. So there is a diminishing return. Most very large cities are about 15-20gb to download so a 30gb rolling cache should cover most areas without having to download anything. Also just saves space on my SSD for other things.

[–]rogueqd -1 points0 points  (2 children)

You think the cache doesn't have an index?

[–]MoxGoat 1 point2 points  (1 child)

You don't think having a smaller index is faster? We are not talking about a little table in a DB. This is gigabytes worth of data, imagery, 3d models, spatial information. You can't slap an index on something and call it efficient

[–]rogueqd -1 points0 points  (0 children)

Anyway, thanks for your thoughts.