工作集和提交大小有什么区别? [英] what's the difference between working set and commit size?

问题描述

在调试 OOM 错误时，工作集和提交大小有什么区别?特别是提交大小的确切含义是什么?

when debugging OOM bugs, what's the difference between working set and commit size? Especially what's the exact meaning for commit size?

推荐答案

从这里，工作集是:

... 物理内存 (RAM) 而不是虚拟地址空间的计数.它代表了进程的有效虚拟地址空间的子集，意思是它可以被引用而不会导致页面错误.

... a count of physical memory (RAM) rather than virtual address space. It represents the subset of the process's virtual address space that is valid, meaning that it can be referenced without incurring a page fault.

提交大小为:

可分页虚拟地址空间的总量，其中没有除了页面文件之外，后备存储被分配.在具有页面文件，它可以被认为是最大的潜在页面文件用法.在没有页面文件的系统上，它仍然被计算在内，但所有这些虚拟地址空间必须完全保留在物理内存 (RAM) 中次.

the total amount of pageable virtual address space for which no backing store is assigned other than the pagefile. On systems with a pagefile, it may be thought of as the maximum potential pagefile usage. On systems with no pagefile, it is still counted, but all such virtual address space must remain in physical memory (RAM) at all times.

因此，您可以将工作集视为已使用的物理内存量，而提交大小表示已使用的虚拟内存量(不包括 DLL 或内存映射文件之类的东西，它们可以由页面以外的文件返回)文件).

So you can think of the working set as the amount of physical memory used, while the commit size indicates the amount of virtual memory used (sans things like DLLs or memory mapped files, which can be back by files other than the page file).

也就是说，在 .NET 中尝试查找内存泄漏"时，这些数字通常没有用.相反，您应该使用第三方内存分析器.

That said, these numbers are not generally useful when trying to find "memory leaks" in .NET. Instead, you should use third-party memory profilers.

这篇关于工作集和提交大小有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！