Dear developers,
We are planning to rewrite the module r.sun for parallel computation and would like to ask you, which platform is more desired by the GRASS community. To our understanding there are two main ways of development. Either we design it for multi-core desktop systems that use shared memory (for example with use of OpenMP) or create module for large clusters with use of MPI library.
Which way do you think would benefit GRASS more?
Best regards
Jan Ruzicka
Ahoj Honzo,
2013/1/29 Ruzicka Jan <jan.ruzicka@vsb.cz>:
We are planning to rewrite the module r.sun for parallel computation and would like to ask you, which platform is more desired by the GRASS community. To our understanding there are two main ways of development. Either we design it for multi-core desktop systems that use shared memory (for example with use of OpenMP) or create module for large clusters with use of MPI library.
just a small note, AFAIR there was similar project (based on OpenCL)
within GSoC 2010 program [1]. Probably someone here know details...
Martin
[1] https://github.com/mailseth/OpenCL-integration-for-GRASS---GDAL
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
I would vote for multicore OpenMP/OPENCL. I just purchased an 8 core AMD Vishera MB and CPU combo for under $300US to use at home , which is faster than the 8 core Xeon server system I used to do statewide solar irradiation modeling at work for a 755 Million cell grid for 365 days (half hour increments) in 2011. With the advances in multicore architecture ( who knows what core densities ARM will bring?) and utilization of the processing elements in video cards, I think you will benefit many more users on going the multicore route.
Doug
On Tue, Jan 29, 2013 at 8:05 AM, Ruzicka Jan <jan.ruzicka@vsb.cz> wrote:
Dear developers,
We are planning to rewrite the module r.sun for parallel computation and would like to ask you, which platform is more desired by the GRASS community. To our understanding there are two main ways of development. Either we design it for multi-core desktop systems that use shared memory (for example with use of OpenMP) or create module for large clusters with use of MPI library.
Which way do you think would benefit GRASS more?
Best regards
Jan Ruzicka
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
–
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
Hi,
OpenMP first to leverage the actual CPU development routes.
OpenCL second to leverage the actual GPU routes.
Cheers,
Yann
On 29 January 2013 19:11, Newcomb, Doug <doug_newcomb@fws.gov> wrote:
I would vote for multicore OpenMP/OPENCL. I just purchased an 8 core AMD Vishera MB and CPU combo for under $300US to use at home , which is faster than the 8 core Xeon server system I used to do statewide solar irradiation modeling at work for a 755 Million cell grid for 365 days (half hour increments) in 2011. With the advances in multicore architecture ( who knows what core densities ARM will bring?) and utilization of the processing elements in video cards, I think you will benefit many more users on going the multicore route.
Doug
On Tue, Jan 29, 2013 at 8:05 AM, Ruzicka Jan <jan.ruzicka@vsb.cz> wrote:
Dear developers,
We are planning to rewrite the module r.sun for parallel computation and would like to ask you, which platform is more desired by the GRASS community. To our understanding there are two main ways of development. Either we design it for multi-core desktop systems that use shared memory (for example with use of OpenMP) or create module for large clusters with use of MPI library.
Which way do you think would benefit GRASS more?
Best regards
Jan Ruzicka
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev–
Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.govThe opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
–
Yann Chemin
Researcher@IWMI
Skype/FB: yann.chemin
I rewrote r.sun into OpenCL a while ago for a google summer of code project. I believe the source is public in github, but never got merged into trunk.
~Seth
via iPhone
On 29 January 2013 19:11, Newcomb, Doug <doug_newcomb@fws.gov> wrote:
I would vote for multicore OpenMP/OPENCL. I just purchased an 8 core AMD Vishera MB and CPU combo for under $300US to use at home , which is faster than the 8 core Xeon server system I used to do statewide solar irradiation modeling at work for a 755 Million cell grid for 365 days (half hour increments) in 2011. With the advances in multicore architecture ( who knows what core densities ARM will bring?) and utilization of the processing elements in video cards, I think you will benefit many more users on going the multicore route.
Doug
On Tue, Jan 29, 2013 at 8:05 AM, Ruzicka Jan <jan.ruzicka@vsb.cz> wrote:
Dear developers,
We are planning to rewrite the module r.sun for parallel computation and would like to ask you, which platform is more desired by the GRASS community. To our understanding there are two main ways of development. Either we design it for multi-core desktop systems that use shared memory (for example with use of OpenMP) or create module for large clusters with use of MPI library.
Which way do you think would benefit GRASS more?
Best regards
Jan Ruzicka
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev–
Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.govThe opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
–
Yann Chemin
Researcher@IWMI
Skype/FB: yann.chemin
Also, OpenCL can run as both multicore CPU and GPU. OpenMP can only run on CPU but it’s much easier to program. I vaguely recall the OpenCL speed up over single thread on the order of 20x - 50x. If you’re looking for a consultant to do additional OpenCL work, I might be able to help.
~Seth
via iPhone
On 29 January 2013 19:11, Newcomb, Doug <doug_newcomb@fws.gov> wrote:
I would vote for multicore OpenMP/OPENCL. I just purchased an 8 core AMD Vishera MB and CPU combo for under $300US to use at home , which is faster than the 8 core Xeon server system I used to do statewide solar irradiation modeling at work for a 755 Million cell grid for 365 days (half hour increments) in 2011. With the advances in multicore architecture ( who knows what core densities ARM will bring?) and utilization of the processing elements in video cards, I think you will benefit many more users on going the multicore route.
Doug
On Tue, Jan 29, 2013 at 8:05 AM, Ruzicka Jan <jan.ruzicka@vsb.cz> wrote:
Dear developers,
We are planning to rewrite the module r.sun for parallel computation and would like to ask you, which platform is more desired by the GRASS community. To our understanding there are two main ways of development. Either we design it for multi-core desktop systems that use shared memory (for example with use of OpenMP) or create module for large clusters with use of MPI library.
Which way do you think would benefit GRASS more?
Best regards
Jan Ruzicka
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev–
Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.govThe opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
–
Yann Chemin
Researcher@IWMI
Skype/FB: yann.chemin
grass-devs,
anyone has a timeline for merging the OpenCL code into trunk?
Cheers,
Yann
On 29 January 2013 21:00, Seth Price <seth@pricepages.org> wrote:
Also, OpenCL can run as both multicore CPU and GPU. OpenMP can only run on CPU but it’s much easier to program. I vaguely recall the OpenCL speed up over single thread on the order of 20x - 50x. If you’re looking for a consultant to do additional OpenCL work, I might be able to help.
~Seth
via iPhone
On Jan 29, 2013, at 8:01 AM, Yann Chemin <yann.chemin@gmail.com> wrote:
Hi,
OpenMP first to leverage the actual CPU development routes.
OpenCL second to leverage the actual GPU routes.Cheers,
Yann
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
–
Yann Chemin
Researcher@IWMI
Skype/FB: yann.chemin
On 29 January 2013 19:11, Newcomb, Doug <doug_newcomb@fws.gov> wrote:
I would vote for multicore OpenMP/OPENCL. I just purchased an 8 core AMD Vishera MB and CPU combo for under $300US to use at home , which is faster than the 8 core Xeon server system I used to do statewide solar irradiation modeling at work for a 755 Million cell grid for 365 days (half hour increments) in 2011. With the advances in multicore architecture ( who knows what core densities ARM will bring?) and utilization of the processing elements in video cards, I think you will benefit many more users on going the multicore route.
Doug
On Tue, Jan 29, 2013 at 8:05 AM, Ruzicka Jan <jan.ruzicka@vsb.cz> wrote:
Dear developers,
We are planning to rewrite the module r.sun for parallel computation and would like to ask you, which platform is more desired by the GRASS community. To our understanding there are two main ways of development. Either we design it for multi-core desktop systems that use shared memory (for example with use of OpenMP) or create module for large clusters with use of MPI library.
Which way do you think would benefit GRASS more?
Best regards
Jan Ruzicka
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev–
Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.govThe opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
–
Yann Chemin
Researcher@IWMI
Skype/FB: yann.chemin