<html><head></head><body><div>Hi, thanks very much Kurt. :D </div><div><br></div><div>Can I exchange an idea with you?</div><div><br></div><div>I’m starting a research to map all Debian packages to determine which are using optimization resources for Intel processors in their source.</div><div><br></div><div>It’s started with a question to know how it’s the best usage for Intel processors and I believe it can allow insights for the community.</div><div><br></div><div>Did you like to comment something or indicate a place where I can share the idea with others?</div><div></div><div><br></div><div>-- Amanda Osvaldo</div><div><br></div><div><br></div><div>On Thu, 2017-05-04 at 13:30 -0700, Kurt Schwehr wrote:</div><blockquote type="cite"><div dir="ltr">Amanda,<div><br></div><div>You can take a look at GDAL if you want to see an example of what a different project has done, you can take a look at:</div><div><br></div><div><a href="https://trac.osgeo.org/gdal/browser/trunk/gdal/alg/gdalwarpkernel.cpp">https://trac.osgeo.org/gdal/browser/trunk/gdal/alg/gdalwarpkernel.cpp</a><br></div><div><br></div><div>Search for USE_SSE and _mm. Being that this is open source, this typically boils down to:</div><div><br></div><div>1. Someone has the time / $ to implement it including tests</div><div>2. The project is willing to accept the contribution and the overhead it may add to the project</div><div><br></div><div>There are a good number of issues hidden in #2.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 2, 2017 at 6:48 PM, Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.com</a>></span> wrote:<br><blockquote type="cite">I can't speak for the developers, but I think it is highly unlikely that they would do anything along these lines if it is not compatible across multiple architectures. There are lots of high performance CPUs/GPUs/etc out there each with their own special requirements. Who is going to fund development, ongoing support, debugging and bug fixing. And you have to have systems with these chips in them to support that. It is costly and time consuming to do this for even one of them. This also puts multiple different execution paths in the code that makes it harder to maintain.<br>
<br>
I think the community would rather the developers make really good, portable, well tested code that works on all platforms, and it release in regular stable way with new geospatial features rather than focus on support one platform in some specialized way instead of doing new feature development.<br>
<br>
My 2 cents anyway.<br>
-Steve<br>
<br>
On 5/2/2017 5:51 PM, Amanda Osvaldo wrote:<br>
<blockquote type="cite">
Hi Steve, more than the compiler it is necessary for the data to fit into the processor correctly.<br>
<br>
And more, I don't have found GPU code yet.<br>
I don't know if it's will take some advantage, however for a large scale processing it should be necessary.<br>
<br>
*Tell me, I not confounding the things?*<br>
<br>
I see Geos has a geometry engine, however, it doesn't mean that it's a high-performance engine or designed for massive computation.<br>
<br>
-- Amanda Osvaldo<span class=""><br>
<br>
On Tue, 2017-05-02 at 14:02 -0400, Stephen Woodbridge wrote:<br>
</span><blockquote type="cite"><span class="">
On 5/2/2017 1:53 PM, Amanda Osvaldo wrote:<br>
<blockquote type="cite">
Hi everybody. I'm reading the Geos source code and have no found any low-level optimization, like the use AVX2 instruction set for Intel processors. It's an important question because without these and others optimization I have no significant difference between a Intel Core and Intel Xeon processors. Can someone tell me if the lack of optimization is intentional or just a lack of programmers? -- Amanda Osvaldo <br>
<br></blockquote>
<br>
<br>
Amanda,<br>
<br>
I would think that this is the responsibility of the compiler, not the<br>
application. I believe you can get an Intel compiler that is designed to<br>
optimize for these various HW differences.<br>
<br>
<a href="https://software.intel.com/en-us/blogs/2013/01/03/free-intel-c-compilers-for-students-and-related-parallel-programming-tools" rel="noreferrer" target="_blank">https://software.intel.com/en-<wbr>us/blogs/2013/01/03/free-intel<wbr>-c-compilers-for-students-and-<wbr>related-parallel-programming-<wbr>tools</a><br>
<br>
-Steve W<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antiviru<wbr>s</a><br>
<br>
______________________________<wbr>_________________<br>
geos-devel mailing list<br>
</span><a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a> <mailto:<a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo<wbr>.org</a>><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geos-devel</a><br>
<br></blockquote><span class="">
<br>
<br>
______________________________<wbr>_________________<br>
geos-devel mailing list<br>
<a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geos-devel</a><br>
<br>
</span><br></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antiviru<wbr>s</a><br>
<br>
______________________________<wbr>_________________<br>
geos-devel mailing list<br>
<a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geos-devel</a></div></div><br></blockquote></div><br><br clear="all"><div><br></div><pre>_______________________________________________
geos-devel mailing list
<a href="mailto:geos-devel@lists.osgeo.org">geos-devel@lists.osgeo.org</a>
<a href="https://lists.osgeo.org/mailman/listinfo/geos-devel">https://lists.osgeo.org/mailman/listinfo/geos-devel</a></pre></div></blockquote></body></html>