Dear All,
In Windows Server, is there any method to permanently change the sequence of allocation of memory for batch process, to allow assigning heap first, before assigning extended memory ?
Reason :
We aware in a 2 processor server, some memory access intensive batch jobs (which do a lot of sorting in memory) would be running sometimes much slower, sometimes much faster (in an order by around 2-3 times). We are suspecting that is due to NUMA effect of varied memory performance, which now undergo further verification test by repetitive testing (running on server with 1 processor socket, vs running on server with 2 processor socket) we are still awaiting the result .
As heap should be "owned" by the worker process itself, so I am guessing if OS would take into account of NUMA and prefer to assign memory "local" to the processor, as long as the requested memory size can fit in that NUMA node. (vs extended memory which is assigned for the whole instance and thus probably not able to take care of locality of every running process) We would also take further test about it through RSMEMORY program then.
However, even if the new sequence has proven any effect, RSMEMORY setting would gone by every time instance restart. So I would like to know if there is chance to persist the sequence