search

charmplusplus / charm

The Charm++ parallel programming system. Visit https://charmplusplus.org/ for more information.
Apache License 2.0
206 stars 50 forks source link

Unify memory pool implementations where possible #105

Open nikhil-jain opened 11 years ago

nikhil-jain commented 11 years ago

Original issue: https://charm.cs.illinois.edu/redmine/issues/105

There are a number of pools to manage memory - mempool, cmipool, pami memory pool etc. We should analyze them and possibly unify them to get one pool.

PhilMiller commented 5 years ago

Original date: 2013-05-29 21:20:21

CmiPool is only used under CONVERSE_POOL in CmiAlloc and in the state-space search engine under an #ifdef there. In the converse use-case, it's never been shown to provide a benefit (per Eric). We should inquire about SSSE (Yanhua, Pritish?), and ditch it if it's not useful there either.

stwhite91 commented 5 years ago

Original date: 2017-02-01 18:44:16

CmiPool is now only used in the state-space search engine, so we don't really need to worry about that one anymore.

"mempool" is used on GNI and by Isomalloc, and Michael is working on generalizing it and using it in Node GPU Manager.

stwhite91 commented 5 years ago

Original date: 2017-02-01 18:56:00

Here's a related patch Nikhil originally wrote to make exceptions for large allocations (to not use the mempool when servicing them): https://charm.cs.illinois.edu/gerrit/#/c/1874/ https://github.com/UIUC-PPL/charm/commit/12f605d286fdd7c13d26322803fd749519be8c2c

stwhite91 commented 5 years ago

Original date: 2017-04-11 21:03:28

https://charm.cs.illinois.edu/gerrit/#/c/2306/