[Tilesathome] API Bottleneck

[Robert (Jamie) Munro]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hakan Tandogan wrote:
>>> Perhaps then all pending priority 2 tiles that are unprocessed each
>>> Wednesday evening could automatically be flagged as being renderable by
>>> the Zappy API.
>> I think that the T at H system should move wholesale to the zappy api. The
>> main API is far too overloaded to support rendering tiles that will
>> probably never be looked at.
> 
> I'm not quite sure about that. One of the unique selling points (at least
> for me) of T at H is that I can update an area and see quite quickly how it
> meshes with the tiles around it.

We need to improve the osmarender plugin for JOSM, so that it uses the
real renderer (i.e. inscape or batik). The advantage of batik is that it
is java, so could probably be incorporated into the jar file download.
It should also incorporates a version of close areas that understands
the bound tag - perhaps this could be ported to java as well.

This would provide instant rendering in JOSM, regardless of editor.

> Usually, I render the tiles I'm currently working on myself and upload
> them to T at H so they don't even enter the public queue. I assume that if I
> can get the area in JOSM, my tileGen.pl should also be able to do so ;-)

Tiles at Home is effectively a large DDOS attack on the main mapping
server. It's fine if it is using a negligible amount of the server's cpu
etc, but as it isn't, in needs to be turned off. Rendering should be
based on planet files, and planet files (or their diffs) should be made
more often. I see no reason why every time the planet making script
finishes it can't be started again, as long as it runs "nice". That way
we would get a planet file every 18 hours or so. I can see that for
clarity, it may be worth restricting it to once a day, but there seems
no point making it happen less often.

Robert (Jamie) Munro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG8ouUz+aYVHdncI0RAjSOAKDWsEkPsE1NLoYwSeQoNqzbQFAaUgCg3YiN
nOF37tiUioAUc7VT78izfKo=
=Ug+T
-----END PGP SIGNATURE-----