[Tilesathome] rendering timeout

[Dirk-Lüder Kreie]

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

Thomas Stets schrieb:
> I remember reading somewhere that there is a 1.5 hour timeout after which
> a tile to be rendered is handed out to another client.
> 
> What does that mean for me (and my aging 2x2.0 GHz G5 PowerMac)? If a tile takes
> several hours to render (Amterdam comes to mind, or 1238,1514, which
> has taken the last 5 hours to render 22% of), should I just abort the job
> and request a new tile, or should I see it through, in case everyone else will
> need just a slong as me?

This Problem is not really well explored as you see by the lack of answers.
There are arguments for both sides (keep running or abort) and the
Server Timeout is actually a moving target.

I'd say if you have a Machine with 2 GB of RAM you should try keeping it
running (the most slowdown is for complex tiles causing inkscape to
swap, so CPU power is only secondary criteria).

- --

Dirk-Lüder "Deelkar" Kreie
Bremen - 53.0952°N 8.8652°E

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHTql9FUbODdpRVDwRAoW3AKC0vweaQBeUtkZgfQ5wLwL+lUIzRgCgtRUZ
Ba3KffJGV9oFyI6FgjsL7Do=
=FUPs
-----END PGP SIGNATURE-----