[Tilesathome] Unnecessary re-rendering ?

Marc Quinton mquinton at gmail.com
Mon Mar 17 13:24:32 GMT 2008


On 3/17/08, Maciek Kaliszewski <mkalkal at interia.pl> wrote:
> Hi,
>  Today my TaH client is rendering  2103,1346 (zoom 12)
>   quite complicated tile (on my AMD64 system with 4Gb of mem it is
>  feasible. Rendering of the tile takes several hours).
>  But information at
>  http://tah.openstreetmap.org/Tiles/info.php?x=2103&y=1346&z=12&layer=tile
>  is a bit confusing .
>
>  Server Time: 2008-03-17 02:43:06
>  Taken by client at 2008-03-17 02:40:32.
>  Taken by client at 2008-03-17 02:52:50.
>  Taken by client at 2008-03-17 02:55:21
>  Taken by client at 2008-03-17 03:08:33.
>  Taken by client at 2008-03-17 03:21:31.
>

I have also tried to render this tileset but could not be able to
finish because of
a "memory allocation error" in Inkscape.

so, when there is an error like this, tileGen.pl detect this error and
put the request back
to the server so that some one else can try it. This tileset is really
large. Not all
computers can render them. It should be interesting to register wich
computer can
and which can't. For my own, I have a single account and many computers, some
can render big tilesets and some won't.

Here is my specifications :
 - each client on any computer should generate an key, or get one from
serveur and should keep that key.
 - each time a client connect to the server, it should pass the key to identify,
 - the server should try to render some taks at different complexity,
 - if the client put back some tileset with "memory fault", the
complexity or size of the tileset should be registrered on server, and
the serveur should try not to give to complexe task given those
information

of course, this task is a little complex for TAH server himself.




More information about the Tilesathome mailing list