Introduce explicit "commit" in OSCompat abstraction of virtual memory about hermes

[haozhun]

To expand on what @tmikov commented.

With NCGen, Hermes reserves memories as 4MB segments. The expected outcome of this issue is not to break down the 4MB at commit time. In fact, I expect "commit" to still happen 4MB at a time. Instead, it is so that vm_unused can have meaningful impact (to reduce RSS) on Windows.

[haozhun]

As part of this task, once vm_unused is implemented, tests that exercised vm_unused can be re-enabled. However, those tests also exercises regionFootprint, which is a test-only function that isn't implemented for Windows. regionFootprint is certainly implementable on Windows.

• Microsoft Sysinternals provide a tool called VMMap, which provides the same kind of info that /proc/self/smaps provides. Screenshot here.
• An open source command line equivalent of VMMap can be found by following links in this stackoverflow question.
• Look for QueryWorkingSet in process_map.cpp in twpol/vmmap.

[tmikov]

I think it is very important to note that Hermes is committing incrementally on Windows, only it is happening with a granularity of a single segment (4MB).

[mganandraj]

Thanks for the clarification. I haven't tested with NCGen yet.
vm_unused implementation would help for long running apps.

[tmikov]

@mganandraj After a full GC we release unused 4MB segments to the OS, so you will get that behavior already, with 4 MB granularity.

[dulinriley]

I think this will actually be more relevant if PreAllocatedStorageProvider is used instead of VMAllocateStorageProvider.

PreAllocatedStorageProvider right now (on Windows) will reserve and commit the whole 500 MB range; however, it could be changed to only reserve the 500 MB range, and commit upon each call to newStorage.

PreAllocatedStorageProvider isn't the default yet for NCGen, but providing some experiments I'm working on go well, we might transition to using that on some platforms.

[tmikov]

Implemented in 043f073