In case there are any NT kernel devs listening: from cold start, an exe that touches ~1gb of memory takes over 100ms to do so due to page handling. With 2MB pages enabled, this drops down to 30ms. This suggests to me that a "MEM_REALLY_COMMIT" VirtualAlloc flag would help?
-
Show this thread
-
Because when you VirtualAlloc 1gb, if we know the total time plus page faulting to use the memory is 30ms with 2MB pages, one assumes that even with 4k pages if VirtualAlloc did the page prep right there in bulk, it could at least provide something closer to 30ms?
1 reply 0 retweets 10 likesShow this thread -
Replying to @cmuratori
Don't you think it's simply the price you have to pay for setting up 512 times as many page table entries? And could PrefetchVirtualMemory help in your case (don't know if you're doing I/O or just reserving pages)?
3 replies 0 retweets 0 likes
PrefetchVirtualMemory makes it slower, since it takes time itself (several milliseconds) and the linear write still goes basically the same speed.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.