专业论文译文-JAVA堆.doc

专业译文: The Java heap The Java heap, where every Java object is allocated, is the area of memory youre most intimately connected with when writing Java applications. The JVM was designed to insulate us from the host machines peculiarities, so its natural to think about the heap when you think about memory. Youve no doubt encountered a Java heap?OutOfMemoryError?— caused by an object leak or by not making the heap big enough to store all your data — and have probably learned a few tricks to debug these scenarios. But as your Java applications handle more data and more concurrent load, you may start to experience?OutOfMemoryErrors that cant be fixed using your normal bag of tricks — scenarios in which the errors are thrown even though the Java heap isnt full. When this happens, you need to understand what is going on inside your Java Runtime Environment (JRE). Java applications run in the virtualized environment of the Java runtime, but the runtime itself is a native program written in a language (such as C) that consumes native resources, including?native memory. Native memory is the memory available to the runtime process, as distinguished from the Java heap memory that a Java application uses. Every virtualized resource — including the Java heap and Java threads — must be stored in native memory, along with the data used by the virtual machine as it runs. This means that the limitations on native memory imposed by the host machines hardware and operating system (OS) affect what you can do with your Java application. This article is one of two covering the same topic on different platforms. In both, youll learn what native memory is, how the Java runtime uses it, what running out of it looks like, and how to debug a native?OutOfMemoryError. This article covers AIX and focuses on the IBM? Developer Kit for Java. Many of the restrictions that a native process experiences are imposed by the hardware, not the OS. Every computer has a processor and some random-access memo