You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chapel applications may want to scale the problem size based on the amount of memory available. Currently, they must rely on locale.physicalMemory, which is what several performance benchmarks do. This is inadequate for several reasons:
The maximum size of the Chapel heap may be constrained by CHPL_RT_MAX_HEAP_SIZE.
Co-locales share physical memory.
If PSHM is enabled in GASNet the locales' heaps are allocated from shared memory, which may be smaller than physical memory.
We need a mechanism for a locale to determine its "fair share" of the physical memory on the node. This is different from the maximum amount of memory that it can allocate because if there are several co-locales without fixed heaps then any one heap can grow to the size of physical memory, but each locale should size itself to use 1/Nth of the physical memory.
All of this would presumably be implemented by adding the appropriate field(s) to Locale; the tricky part is which fields to add.
The text was updated successfully, but these errors were encountered:
Chapel applications may want to scale the problem size based on the amount of memory available. Currently, they must rely on
locale.physicalMemory
, which is what several performance benchmarks do. This is inadequate for several reasons:CHPL_RT_MAX_HEAP_SIZE
.We need a mechanism for a locale to determine its "fair share" of the physical memory on the node. This is different from the maximum amount of memory that it can allocate because if there are several co-locales without fixed heaps then any one heap can grow to the size of physical memory, but each locale should size itself to use 1/Nth of the physical memory.
All of this would presumably be implemented by adding the appropriate field(s) to
Locale
; the tricky part is which fields to add.The text was updated successfully, but these errors were encountered: