4 ms·
It's basically paging to disk. Not necessarily memory savings, but the improvements here are that it will run on computers with less ram because it can page to
by rovr138 4y ago
It's basically paging to disk.
Not necessarily memory savings, but the improvements here are that it will run on computers with less ram because it can page to disk.
Not necessarily the number reported (since you do need to load chunks into ram), but still lower.
- chaboud 4y agoSort of, but without the duplication and initial wait to load. A traditional fat in-memory app would do this: file (DISK) to process active pages (RAM) to paged out virtual memory if saturated (elsewhere on DISK) Using mmap typically goes something like: file (DISK) to process active pages (RAM) to released and cached (RAM) to uncached if evicted (back to same place on DISK) OR back to process active pages from cache (RAM) For the cost of fixing up some process page tables, the physical memory pages necessary can be brought back from the cache rather than read from disk. It's an orders-of-magnitude performance savings.
- detrites 4y agoIf that's the case then part of this may be the different interpretations of "memory". One persons "paging the same memory requirement from disk to RAM" can be someone elses "requiring less memory/RAM".