| Title | Purpose of manual pool classes is unclear |
| Status | closed |
| Priority | nice |
| Assigned user | Richard Brooksby |
| Organization | Ravenbrook |
| Description | When you want a manual variable-size pool class, which one should you use? It's not clear how to choose between MV, MVT or MVFF. |
| Analysis | There are some points of difference: 1. MVT doesn't support allocation via mps_alloc and so doesn't support structured allocation caches (but this would be easy to add). 2. MV doesn't support allocation points or allocation frames (but this would be easy to add). 3. MVFF and MVT have configurable alignment (MV uses natural word size). I think the key use cases are: * MV: simple and rock-solid (but maybe not very fast) * MVT: temporal lifetimes: objects that are born together die together * MVFF: other lifetime patterns |
| How found | inspection |
| Evidence | None. |
| Observed in | 1.110.0 |
| Created by | Gareth Rees |
| Created on | 2012-10-31 15:51:17 |
| Last modified by | Gareth Rees |
| Last modified on | 2013-06-08 17:49:26 |
| History | 2012-10-31 GDR Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 182636 | closed | 2013-06-08 17:49:26 | Gareth Rees | Separate the consideration of automatic and manual pool classes, so that we can ask the appropriate questions in each case. |