[Tilesathome] How to store blank tiles revisited

[Jocelyn Jaubert]

Hi,

Le 28 avril 2008, Sebastian Spaeth a écrit :
> currently the t at h server stores blank tiles in the server database
> and lookups bubble up recursively until we find a blank tile info.
> 
> I am currently rethinking the t at h server setup and would like to know
> if people have ideas on what would be the optimal way to store
> blankness information (blank sea vs blank land). We need to optimize
> for quick lookup of course, as that is a time critical action for the
> slippy map. At the same time we cannot afford to store blankness info
> for each and every tile in the db.
>
> If people have ideas, feel free to propose them

If I understand correctly how t at h works, blank tile are only used for
showing on the slippy map, and they are "generated" by clients.

So, could it be possible to use symbolic (or maybe hard) links to store
this information ?

That will remove the bottleneck you are talking about, but might use
too many inodes (hard links shouldn't use any inode nor disk space, so
might be a better idea)

If you need help on how to implement this, I can take a look at the
server code.


There must be a reason it won't work, but please be free to shout on
me :)

Thanks,
Jocelyn