一旦应用程序启动并运行，内存利用就将受到系统需要的对象的数量和大小的影响。
Once an application is up and running, memory utilization is affected by the number and size of objects the system requires.
使用任何超量使用机制都会从根本上影响主机和客户内存管理系统的运行。
The use of any overcommitment mechanism fundamentally affects the operation of the host and guest memory management systems.
在POWER 7系统上运行的大内存工作负载会受益于此特性。
Large memory workloads running on POWER7 systems benefit the most from this feature.
同样，测试完成的详情包括每次运行后的内存泄漏分析的结果。
Also, the test completion details included the results of memory leak analysis following each run.
直到现在你都被限制只能安装和运行程序在G1内置内存里。
Until now, you were limited by the G1's built-in memory for installing and running programs.
例如，你的程序运行耗尽内存，或者遇到被零除。
For example, your program runs out of memory or encounters divide-by-zero.
传统上，配置数据库内存参数以优化运行性能是一项复杂而耗时的任务。
Traditionally, configuring database memory parameters for optimal operation can be a complex and time-consuming task.
对它运行一些事件，观察它加载类、编译字节代码以及管理内存。
Run some events through it, watch it load classes, compile bytecode, and of course, manage memory.
运行与测试无关的其他应用程序将引入针对本地CPU、内存和磁盘资源的竞争。
Having other applications also running that are unrelated to the testing introduces competition for local CPU, memory and disk resources.
显然，由于同时在运行多个程序，所以每个进程不可能拥有全部内存。
Obviously, since you are running multiple programs at the same time, each process can't own all of the memory.
使用32MB内存来运行模拟机器的那些人不可能运行最新版本的KDE。
Someone running an emulated machine with 32 MB of memory is unlikely to run the latest version of KDE.
在多个JVM中运行示例程序时，很容易看出虚拟内存的节省。
It is also easy to see the virtual memory savings when running the example program in more than one JVM.
每个额外的递归调用都会占用更多的内存，从而减慢浏览器的运行。
Each additional recursive call takes up memory, and eventually will slow down the browser.
如果不使用标记组，则返回的数据将只包括在运行脚本内使用的内存，减去内存管理器开销。
Without the flag set, the data returned would be only the memory used within the running script, minus the memory-manager overhead.
这些转储文件包含了运行中应用程序的完整内存镜像—所有信息和数据都采用hprof格式表示，包括所有原生内存和线程信息。
These dumps contain the entire memory image of the running application - all the information and data in the HPROF format, as well as all of the native-memory and thread information.
由于我们是在生产服务器中运行的，并尝试检测内存泄漏(而不是造成内存泄漏)，所以我们只能存储非常有限的数据量。
Since we are running within a production server, and are trying to detect memory leaks (not create them), we have to store a very limited amount of data.
不过，对于那些在大量进程在运行的系统来说，将页表存储到高端内存中可以在低端内存区域挤出更多的内存。
However, for systems in which a large number of processes are running, storing page tables in high memory can be enabled to squeeze more memory out of the low memory area.
可能需要更多的内存来支持在本地运行或作为存储过程运行的应用程序。
More memory may be needed to support applications that run locally or as stored procedures.
图3显示了运行上述示例代码的结果，其中显示了“内存条件：内存溢出”条件的结果。
Figure 3 shows the results of running the example code above, showing the results of a "memory condition: memory leak" condition.
管理员能够在测试或生产环境中运行轻量级内存泄漏检测，并可以在早期接收内存泄漏的通知。
Administrators are able to run lightweight memory leak detection in test and production environments and receive early notification of memory leaks.
这些运行时例程的地址可能在每次将JVM加载到内存时变化。
These runtime routines' addresses can be different each time the JVM is loaded into memory.
重要运行时参数的度量，包括内存使用、性能和代码覆盖。
Measurement of vital runtime parameters, including memory usage, performance, and code coverage.
你能肯定的知道正在运行的服务里面没有内存泄露吗？
Do you know for sure that there aren't any memory leaks in your running services?
设备驱动处于内核之上，运行在用户态。每个驱动都作为单独的进程运行，受到内存管理硬件的严格约束，只能访问自己拥有的内存。
Above the kernel, running in user mode, are the device drivers, each one running as a separate process tightly restricted by the memory management hardware to accessing only its own memory.
当运行时，子系统的共享内存包含了实际有用的配置信息。
When running, the subsystem's shared memory contains the actual usable configuration information.
这带来了一种很有趣的运行应用程序的方式：如果应用程序有内存泄露，或者消耗了太多的内存，只需终止它随后重启即可。
That lead to an interesting approach to running an application and on its design: if the app has memory leaks or consumes too much memory, they simply killed it and restarted it from scratch.
您可以为运行在集群中的应用程序选择数据库会话持久化或内存到内存的会话复制。
You can choose from database session persistence or memory-to-memory session replication for applications running in a cluster.
通过定义好的路径——在当前情况下是运行时——访问内存，核心可以验证代码并没有访问不该访问的内存位置。
By accessing memory through well-defined paths, the runtimes or in this case, kernels can verify that code is not accessing memory locations to which it should not have access.
此计算机需要更多的内存或者减少正在运行的程序。
This machine needs either more memory or fewer programs running.
在不考虑数据库运行所需的额外硬件的情况下，数据库持久性的性能也好于内存到内存复制。
The performance of database persistence is also better than memory to memory replication, when not taking the extra hardware that the database is running on into account.
应用推荐