[Tilesathome] Slow name collision detection

[Jiri Klement]

There was a little bug in orp.pl which caused proximity calculation
for every node in file, not only nodes with captions. It should be
fixed now.

On Wed, Aug 6, 2008 at 3:18 PM, Andreas Mueller
<mailinglists at andreas-mueller.com> wrote:
> --On Mittwoch, 06. August 2008 12:25 +0200 "\"Marc Schütz\""
> <schuetzm at gmx.net> 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
> Tilesathome at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/tilesathome
>