--On Mittwoch, 06. August 2008 12:25 +0200 "\"Marc Schütz\"" <[EMAIL PROTECTED]> wrote:
> The new proximity filter is extremely slow (at least for the tilesets > I tried it on, e.g. 2180,1374 and 2151,1475). It takes many times > longer than rendering itself (e.g. 20min filtering vs. 3min > rendering). Is this a bug or is it due to the algorithm being > inefficient? 20 minutes is really bad for those tiles... The current tile which is rendered on my computer is the center of Toulouse: <http://tah.openstreetmap.org/Browse/details/tile/12/2064/1495/> Both orp.pl processes are about to reach 1 hour CPU time right now, running on an Athlon64 X2 5600+. I don't think that this tile will be finished within the default 6 hours timeout. Andreas. _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
