括号中显示了控制这些内存池大小的配置参数。
The configuration parameters that control the sizes of these memory pools are shown in parenthesis.
这些内存区域称为作用域内存和不朽内存。
These memory areas are referred to as scoped and immortal memory.
首先，分配所有这些内存，这不是免费的。
下一篇文章我们将讨论系统内核是如何跟踪这些内存区域的。
The next post discusses how the kernel keeps track of these memory areas.
下一篇文章将讨论内核是如何跟踪这些内存区域。
The next post discusses how the kernel keeps track of these memory areas.
这些内存设置对JVM在用尽内存时所执行的操作有直接影响。
These memory Settings have a direct impact on what the JVM does when it runs out of memory.
当您确定本机内存耗尽时，下一个逻辑问题是：谁在使用这些内存？
Once you have determined you are running out of native memory, the next logical question is: What's using that memory?
这些内存必须使用低端内存，而这在32位硬件上有点不够用。
This memory must also come from low memory, which on 32-bit hardware is somewhat limited.
这些内存区域，对操作系统来说，最多也就是连续的字节序列。
These memory areas, as far as the operating system is concerned, are contiguous sequences of bytes.
由于这些内存问题，在本文的其余小节中，我将假定该程序使用了一种垃圾收集器。
Because of these memory issues, I'll assume in the remainder of the article that there is a garbage collector with the programs.
但是得到的结果可能会造成误解，因为它并不意味着进程要消费所有这些内存占用。
However, the resulting number could be misleading because it doesn't mean that the process is consuming all that footprint.
参数- mx告诉jvm堆有多大，但JVM通常不在一开始就分配所有这些内存。
The -mx parameter to the JVM tells it what the maximum size of the heap should be, but the JVM often doesn't allocate all that memory at the start.
这是因为内核驱动程序需要访问这些内存，在此期间这些页面不能交换出去。
They need to be locked because the memory will be accessed by kernel-mode drivers and cannot be paged out for the duration of the access.
在这种情况下需要一个解析器，该解析器可以根据这些内存转储生成有意义的日志消息。
A parser is required in such cases, which generates meaningful log messages out of those memory dumps.
不管最新的超大机器上有多少内存，很快就会发现新应用程序已占满了这些内存。
No matter how much memory your latest super machine has, you will soon find new apps to fill it with.
由于这些内存段的大小不是固定的，我们只能估计实例共享内存和数据库共享内存的大小为。
Since the sizes of all these memory segments are not fixed, we can only estimate the size of the instance and database Shared memory to be.
如果垃圾收集器需要释放堆中的内存，则这些内存区域将允许任务使用内存而不需要中断任务。
These areas allow tasks to use memory without being required to block if the garbage collector needs to free memory in the heap.
这些内存块的默认分区大小为每块256KB，但是您可以调整这些分区大小以满足特殊需求。
The default size of these memory segments is 256 KB per block, but you can adjust these to suit your particular needs.
您可能会忘了跟踪所有指针（指向这些内存位置），并且某些内存段没有释放，还保持分配给该程序。
You might forget to keep track of all the pointers (pointing to these memory locations), and some of the memory segments are not freed and stay allocated to the program.
希望分配了大量连续内存区域但这些内存不马上同时使用的程序常常结合使用保留内存和提交内存。
Programs that want to allocate a large and contiguous area of memory but don't need it all immediately often use a combination of reserved and committed memory.
它必须足够大以适应所有用户的内存映像复制份数，并且他必须提供直的通路以适应这些内存映像。
It must be large enough to accommodate copies of all memory images for all users, and it must provide direct access to these memory images.
当达到几十万链接的时候，这些累计起来达好几个G——这些内存其实可以更好地用于存储用户数据。
When you get into hundreds of thousands of connections, this adds up to gigabytes of memory — memory that could be better used to store user data.
以后活动数据数量增加，堆需要扩展，JVM可以再提交多一点内存，这些内存与当前提交的部分相邻。
Later, when the amount of live data grows and the heap needs to be expanded, the JVM can commit a little more, adjacent to the currently committed area.
此外，因为文字块数据存储在内存中，这些内存数据在写到磁盘之前，不必或只需作很少更改，大大减少了CPU开销。
In addition, because the literal block data is stored in memory, little or no massaging of the in-memory data is required before writing it to disk, greatly reducing CPU overhead.
RAMBack导致Firefox发出一个释放内存的内部通知（否则这些内存将用于提高性能）。
RAMBack causes Firefox to issue an internal notification to free up memory that is otherwise held for performance purposes.
CLR里面的垃圾回收机制用一定的算法判断某些内存程序不再使用，回收这些内存并交给我们的程序再使用。
The Garbage colleciton of CLR adopts algorithms to decide which part of memory the program does not need any more, and then release these memory for further use.
Windows通常不会允许您访问地址空间中的所有这些内存，进程自己使用的只有不到一半，其他供Windows使用。
Windows doesn't usually let you access all of the memory in this address space; your process gets just under half for its own private use, and Windows USES the rest.
解析查询和优化都需要内存。这些内存通常比较小，可以忽略，不过如果是某些查询在这个步骤中则需要大量内存，尤其是那些设计的比较特别的查询。
Query Parsing and optimization needs memory. This is usually small to be ignored but certain queries can have very large memory requrement for this step, especially specially crafted ones.
由于每个节点都只能访问自己的内存，如果其他节点需要访问这些内存中的数据，就必须对这些数据结构进行复制并通过网络进行传送，这会导致大量的网络负载。
Because each node has access to only its own memory, data structures must be duplicated and sent over the network if other nodes want to access them, leading to network overhead.
这些数据存储在计算机的内存中。
应用推荐