Reduce the number of proxies constructed in the case with gravity
1 unresolved thread
1 unresolved thread
Three main changes:
- Loop over neighbouring cells in the same way when making proxies, constructing hydro tasks and gravity tasks,
- Use a symmetry condition to reduce the number of proxies on a given node,
- Use a better calculation of the distance between future multipoles to decide whether to construct a proxy or not.
Overall this reduces the number of gravity proxies by a factor 6 or so on the EAGLE-50 example.
Merge request reports
Activity
- Resolved by Matthieu Schaller
mentioned in merge request !672 (merged)
- Resolved by Matthieu Schaller
- Resolved by Matthieu Schaller
1899 1879 s->nr_cells, 1, 0, e); 1900 1880 } 1901 1881 1882 if (e->verbose) 1883 message("Making stellar feedback tasks took %.3f %s.", 1884 clocks_from_ticks(getticks() - tic2), clocks_getunit()); 1885 1886 tic2 = getticks(); 1887 1902 1888 /* Add the self gravity tasks. */ 1903 if (e->policy & engine_policy_self_gravity) engine_make_self_gravity_tasks(e); 1889 if (e->policy & engine_policy_self_gravity) { 1890 threadpool_map(&e->threadpool, engine_make_self_gravity_tasks_mapper, NULL, added 1 commit
- 1f726a7c - Cleaner breacketing in the pair-task creation.
LGTM, handing off to @pdraper!
assigned to @pdraper
added 29 commits
-
1f726a7c...e1bdccb3 - 28 commits from branch
master
- 037b06ba - Merge branch 'master' into proxy_work2
-
1f726a7c...e1bdccb3 - 28 commits from branch
mentioned in commit f39b0ff5
Please register or sign in to reply