<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Uli + Steve,</p>
<p><br>
</p>
<p>reg. config files: I think the file .classpath should also be changed to state 1-8, see attached patch.</p>
<p><br>
</p>
<p>Gerd<br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von UliBaer <ulibaer@gmail.com><br>
<b>Gesendet:</b> Dienstag, 2. August 2016 18:11:34<br>
<b>An:</b> mkgmap-dev@lists.mkgmap.org.uk<br>
<b>Betreff:</b> Re: [mkgmap-dev] Move to Java 1.8</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Gerd Petermann wrote<br>
> Hi Uli,<br>
> <br>
> thanks for the patch. I tried it and found no significant change in run<br>
> time<br>
> or memory usage.<br>
> My test case: Compile 9 tiles (a part of the Britisch Isles) (with<br>
> --max-jobs on 4 cores)<br>
> In what scenario do you think that the stream methods should save time?<br>
> <br>
> My understanding is that the list streaming is better as it allows<br>
> automatic<br>
> use of multiple cores, so I'd expect improvements in e.g. the gmapsupp<br>
> builder<br>
> which uses a single thread, but not in the code which compiles the tiles.<br>
> On the other hand, the combiners which run single threaded are probably<br>
> more I/O bound.<br>
> <br>
> Gerd<br>
<br>
Hi Gerd,<br>
<br>
the patch only used the sequential .stream(). method. If you want to use<br>
multiple cores, simply replace the .stream(). with .parallelStream(). and<br>
the jvm tries to work parallel pipelines with multiple threads. You only<br>
have to be aware, that the order of processing is completely arbitrary in<br>
that case, so the atomic operations have to be independent of each other and<br>
not depend on the order of execution. Also the order of elements in the<br>
resulting list is arbitrary. This can be worked around by using a SortedList<br>
for the collection or by using .sorted((o1, o2) -><br>
o1.getField().compareTo(o2.getField())). near the end of the streaming<br>
pipeline.<br>
<br>
Best regards, Uli<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://gis.19327.n5.nabble.com/Move-to-Java-1-8-tp5879546p5879702.html">
http://gis.19327.n5.nabble.com/Move-to-Java-1-8-tp5879546p5879702.html</a><br>
Sent from the Mkgmap Development mailing list archive at Nabble.com.<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</div>
</span></font>
</body>
</html>