Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2626: Multipole is not OpenMP parallelized
by Gabriele Bozzola 04 Aug '22

04 Aug '22

#2626: Multipole is not OpenMP parallelized Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: enhancement Priority: trivial Component: Comment (by Gabriele Bozzola): I was looking at the inner function `Multipole_Integrate` \(ie, fixed a radius, l, and m\). I think that loops there \(which are over theta and phi\) can be parallelized with no problems. However, you are probably right and the simplest thing to do would be to add pragmas over l and m. The function call is ``` for (int l=0; l <= lmax; l++) { for (int m=-l; m <= l; m++) { // Integrate sYlm (real + i imag) over the sphere at radius r Multipole_Integrate(array_size, ntheta, reY[si][l][m+l], imY[si][l][m+l], real, imag, th, ph, &modes(v, i, l, m, 0), &modes(v, i, l, m, 1)); }//loop over m }//loop over l ``` `Multipole_Integrate` does not touch any input except the last two, so the input can be shared. `modes` is a custom class that contains all the output data and `&modes(v, i, l, m, 0)` is just a pointer to a `CCTK_REAL`. Different iterations are going to have different pointers, so I think that the iterations are all independent without making any change. `l`and `m` are already private, so, probably to parallelize the entire thorn we just need to add `#pragma omp for collapse(2)` \(Plus, we’d have to remove an inner pragma in one of the integration methods\) > You may actually see an extra speedup, if you are using it, by switching from ASCII output to HDF5 output. Yes, I am already doing that \(which, incidentally, speeds up significantly kuibit as well\). ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2626/multipole-is-not-…

1 0

#2626: Multipole is not OpenMP parallelized
by Roland Haas 04 Aug '22

04 Aug '22

#2626: Multipole is not OpenMP parallelized Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: enhancement Priority: trivial Component: Comment (by Roland Haas): If the loops \(e.g. the ones over radii\) contain calls to the interpolator then they cannot be OpenMP parallelized, since the interpolator \(no Cactus call actually\) is not thread save. One would have to MPI parallelize but that is not trivial since the interpolator is a MPI collective call \(but different ranks may pass different arguments, so what is needed is “dummy” interpolator calls on those ranks that have run out of radii to work on\). It is also not fully clear if this would speed up \(or not, if the inter-process communication actually dominates\). The loops over \(l,m\) can be OpenMP parallelized \(no interpolator call there\) can be parallelized using OpenMP \(though watch out for shared temporary arrays and static variables\). You may actually see an extra speedup, if you are using it, by switching from ASCII output to HDF5 output. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2626/multipole-is-not-…

1 0

#2626: Multipole is not OpenMP parallelized
by Gabriele Bozzola 04 Aug '22

04 Aug '22

#2626: Multipole is not OpenMP parallelized Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: enhancement Priority: trivial Component: The `Multipole` thorn is completely serial, while being essentially a series for loops that could be easily parallelized with OpenMP. \(In one of my typical BBH simulation, `Multipole` is of order of 1-2 % of the execution time.\) ‌ ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2626/multipole-is-not-…

1 0

#2598: thornyflat - production run segmentation fault
by Anuj Kankani 04 Aug '22

04 Aug '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Anuj Kankani): Got it, thank you for all the help. Sorry for the mistakes, I don’t have much experience with git/bitbucket. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Roland Haas 04 Aug '22

04 Aug '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Roland Haas): the way to do it is: 1. fork the simfactory repo on bitbucket 2. create a branch in your fork with the files you want 3. create the pull request in your fork, it will show up in the list of pull requests in the source repository ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Anuj Kankani 04 Aug '22

04 Aug '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Anuj Kankani): It says I do not have permission to create a pull request? ![](https://bitbucket.org/repo/8zBLME5/images/3662654834-permission.png) ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Roland Haas 04 Aug '22

04 Aug '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Roland Haas): You can however create a pull request :slight_smile: I’ll add you with write permission after the pull request. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Anuj Kankani 04 Aug '22

04 Aug '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Anuj Kankani): Ok that’s what I thought I was supposed to do, but I don’t have permissions for the simfactory2 repo so I can’t create a new branch/pull request. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Roland Haas 04 Aug '22

04 Aug '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Roland Haas): They go into the directories “mdb/machines”, “mdb/runscripts”, “mdb/submitscripts” and “mdb/optionlists”. So not one directory per machine but one directory per file type. The files are actually part of simfactory not the testsuite results. So the pull request would have to be for [https://bitbucket.org/simfactory/simfactory2/](https://bitbucket.org/simfac… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

#2598: thornyflat - production run segmentation fault
by Anuj Kankani 04 Aug '22

04 Aug '22

#2598: thornyflat - production run segmentation fault Reporter: Maria Status: new Milestone: Version: ET_2021_11 Type: bug Priority: major Component: Comment (by Anuj Kankani): I created my own branch in order to submit a pull request, but I didn't see a folder for the cluster files. I have added a folder with the files and submitted the pull request and put you as the reviewer. Hopefully this is ok. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-produc…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac