Beginner quesiton memory allocation c++

I’am currently learning c++. During some heap allocation exercises I tried to generate a bad allocation. My physical memory is about 38GB. Why is it possible to allocate such a high amount of memory? Is my basic calculation of bytes wrong? I don’t get it. Can anyone give me a hint please? Thx.

#include <iostream>


int main(int argc, char **argv){
    const size_t MAXLOOPS {1'000'000'000};
    const size_t NUMINTS {2'000'000'000};
    int* p_memory {nullptr};

    std::cout << "Starting program heap_overflow.cpp" << std::endl;
    std::cout << "Max Loops: " << MAXLOOPS << std::endl;
    std::cout << "Number of Int per allocation: " << NUMINTS << std::endl;

    for(size_t loop=0; loop<MAXLOOPS; ++loop){
        std::cout << "Trying to allocate new heap in loop " << loop 
                << ". current allocated mem = " << (NUMINTS * loop * sizeof(int)) 
                << " Bytes." << std::endl;

        p_memory = new (std::nothrow) int[NUMINTS];
        if (nullptr != p_memory)
            std::cout << "Mem Allocation ok." << std::endl;
        else {
            std::cout << "Mem Allocation FAILED!." << std::endl;
            break;
        }
    }
    return 0;
}

Output:

...
Trying to allocate new heap in loop 17590. current allocated mem = 140720000000000 Bytes.
Mem Allocation ok.
Trying to allocate new heap in loop 17591. current allocated mem = 140728000000000 Bytes.
Mem Allocation FAILED!.

>Solution :

Many (but not all) virtual-memory-capable operating systems use a concept known as demand-paging – when you allocate memory, you perform bookkeeping allowing you to use that memory. However, you do not reserve actual pages of physical memory at that time.¹

When you actually attempt to read or write to any byte within a page of that allocated memory, a page fault occurs. The fault handler detects that the page has been pre-allocated but not demand-paged in. It then reserves a page of physical memory, and sets up the PTE before returning control to the program.

If you attempt to write into the memory you allocate right after each allocation, you may find that you run out of physical memory much faster.

Notes:

¹ It is possible to have an OS implementation that supports virtual memory but immediately allocates physical memory to back virtual allocations; virtual memory is a necessary, but not sufficient condition, to replicate your experiment.

One comment mentions swapping to disk. This is likely a red herring – the pagefile size is typically comparable in size to memory, and the total allocation was around 140 TB which is much larger than individual disks. It’s also ineffective to page-to-disk empty, untouched pages.