[Tilesathome] t at h server performance

[Martijn van Oosterhout]

On Jan 8, 2008 11:54 AM, Sebastian Spaeth <Sebastian at sspaeth.de> wrote:
> Martijn van Oosterhout wrote:
> Would be great if you could check that in if you are sure that it works.
> There is a trade off between the number of entries and the number of
> look-ups required. Do we wan to remove all unneccessary entries or do we
>   want to keep all, say, z12 entries to make z17 lookups not too slow?

I asked crschmidt and he suggested that the DB is fast enough to
handle many such lookups. I was thinking of combining it with some
caching in the lookup handler. If a *user* (not a script* accesses a
blank tile at z17 and it recurses higher that z14, place an entry in
the DB at z15. This would mean that areas people look at often will
still be fast. But I think maybe we should cross that bridge when we
come to it (the lookup code could be optimised also).

> > The way it's setup is a sort of daemon that monitors for newly
> > uploaded tilesets and optimises them straight away. It's quite quick
> > so eventually I'll probably run it over the entire DB and see how it
> > goes. If you're interested I can check it into SVN, maybe you can
> > check it for bugs...
>
> would be good. let me know if and where you check it in.

I was going to then wasn't sure where. I'm thinking in the Tools
directory in the server stuff, even though it's not a PHP script.

Have a nice day,
-- 
Martijn van Oosterhout <kleptog at gmail.com> http://svana.org/kleptog/