Jump to content

jamie

Members
  • Posts

    2
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Hi Padishar, and thanks for your work on this. I not much of an expert on memory utilisation and only understand what garbage collection is and what MemGraph does in a very basic manner, so this might be a dumb question. I've noticed that using the alt+end function to pad the heap also increases the minimum heap size. This can be quite sizeable; for example in my current modded build, the Heap Min value jumps from 1392MB to 3280MB following the first iteration of heap padding (the first alt+end activation). Following iterations increase the Heap Min value only fractionally. Although heap padding increases the Heap Max value by a larger amount and I therefore get a longer GC interval, a sizeable chunk of the extra allocated memory is eaten up instantly due to the increase in the Heap Min value, and the gains are therefore significantly diminished. My question is: is the Heap Min value meant to increase during the padding process, and is there any way to minimise this increase? FYI, I found that Contract Configurator was creating a disproportionately large amount of garbage in my modded build. I think it was creating around half as much garbage as all of my other mods (around 60) combined, and therefore removed it from my build. This mod has been mentioned elsewhere in this thread, but I just thought I'd mention it again as it had such a significant impact on the stutter problem for me. Thanks! Jamie.
×
×
  • Create New...