Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Understanding page faults and memory swap-in/outs: when should you worry?
1 view
Skip to first unread message
amin...@gmail.com
Dec 2, 2019, 1:43:07 PM12/2/19
to
Hello,
Understanding page faults and memory swap-in/outs: when should you worry?
Read more here:
https://scoutapm.com/blog/understanding-page-faults-and-memory-swap-in-outs-when-should-you-worry
Thank you,
Amine Moulay Ramdane.
Understanding page faults and memory swap-in/outs: when should you worry?
Read more here:
https://scoutapm.com/blog/understanding-page-faults-and-memory-swap-in-outs-when-should-you-worry
Thank you,
Amine Moulay Ramdane.
Bonita Montero
Dec 2, 2019, 2:05:30 PM12/2/19
to
The writer of this article seems a bit confused:
1. Copy on write isn't made on any memory that is allocated.
Memory that is allocated is simply overcommited, that has
nothing to do with copy on write.
2. It's not generally a problem if the virtual address-space
of all processes is larger than the pyhsical memory. It may
be that there are a lot of not written pages which haven't
been associated with individual pyhsical pages. In this case
there's a large overcommit-space.
1. Copy on write isn't made on any memory that is allocated.
Memory that is allocated is simply overcommited, that has
nothing to do with copy on write.
2. It's not generally a problem if the virtual address-space
of all processes is larger than the pyhsical memory. It may
be that there are a lot of not written pages which haven't
been associated with individual pyhsical pages. In this case
there's a large overcommit-space.
0 new messages