Hi WanMil, I tried it and did not see a signficant change in runtime for my data. It seems that the reduce() method is too complex to save time. If you could change the elementMap to two lists this might be easier, but maybe it makes other methods slower...
Ciao, Gerd WanMil wrote > > Hi, > > I implemented a shrinking remove in the elementquadtree which is used by > the LocationHook. If enough elements have been removed the depth of the > quadtree is shrinked. > > Sometimes this improves the performance, sometimes not. > > The patch seems to be not 100% correct because I do get different > numbers of query results from the quadtree (patched finds 24974922 in 66 > tiles, unpatched finds 24974934 elements in 66 tiles). > > > WanMil > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > -- View this message in context: http://gis.638310.n2.nabble.com/PATCH-v1-Remove-shrinks-quadtree-tp7173999p7175567.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
