Hi Uli,
thanks for the patch. I tried it and found no significant change in run time or memory usage. My test case: Compile 9 tiles (a part of the Britisch Isles) (with --max-jobs on 4 cores) In what scenario do you think that the stream methods should save time? My understanding is that the list streaming is better as it allows automatic use of multiple cores, so I'd expect improvements in e.g. the gmapsupp builder which uses a single thread, but not in the code which compiles the tiles. On the other hand, the combiners which run single threaded are probably more I/O bound. Gerd ________________________________ Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von UliBaer <ulib...@gmail.com> Gesendet: Dienstag, 2. August 2016 10:53:15 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Move to Java 1.8 Gerd Petermann wrote > Hi Uli, > > thanks for the hint. I'll experiment with this in future. At the moment I > don't know > of any bottlenecks which could be solved by this. > > Gerd Hi Gerd, yesterday evening i played a little bit with list streaming and found an (albeit small) speed increase in modifying some source code. Unfortunately the loop code is mainly not written in a "streaming friendly" way, e. g. with lots of local variable access inside the loop. I have attached a patch out of eclipse against version 3688. If i find more time, i'll dig deeper into that. Best regards, Uli Attached patch: patch.txt <http://gis.19327.n5.nabble.com/file/n5879637/patch.txt> -- View this message in context: http://gis.19327.n5.nabble.com/Move-to-Java-1-8-tp5879546p5879637.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
