Large JVM Memory and Garbage Collection

Author: artima.com | Published: 5th Jul 2008 | Visited: 372 times | Add Comment
Filed in: Core Java

Although physical RAM is inexpensive, allocating large of amounts of memory to a JVM instance is not generally a good idea, says Azul CTO Gil Tene in this interview with Artima. Tene shows how recent research in garbage collection and JVM implementation helps overcome the memory barrier, resulting in new types of applications.

Read Article

Sponsored Links

• How to load entire database into memory Hi Tom, I have an Oracle Database 8.1.7.4 Standard Edition installed on a Windows 2000 Server. My question is for curiosity more than need. Let's assume that we have enough physical memory and that we can guarantee that the server will neve ...

• Calculating Percentiles in Memory-bound Applications How to compute percentiles of a stream of data too large to fit into memory at ...

• Article :: Understanding Memory Technology Devices in Embedded Linux This chapter uses the example of a Linux handheld to learn about the Memory Technology Devices subsystem of the embedded Linux ker ...

• C++ Memory Management Innovation: GC Allocator Most of the C++ programmers do not benefit from "Garbage Collection" technique (GC). Here is a new memory management technique named "GC Allocat ...

• Heap Memory Manager and Garbage Collector Descripes a module to track heap memory allocations and to avoid memory le ...

• The Frog Race: The desire for control and how large companies interact with standards organizations I was told recently that of the 250 or so standards that Ecma has successfully had accepted by National Bodies at ISO/IEC, only three of them have failed. I thought it would be interesting to read up a little mor ...

• Binding a generic collection to a DataGridView via Visual Basic 2008 code Supply the designer lack of binding a generic collection to a DataGridView in VB 2008, with a few lines of ...

• Memory Leak/Slow Response QC#: 56237 Version: 11.2 Status: Open defect, requires resolution Descripti ...

• Memory leak when dynamically loading DLL with Dialogs unit uses QC#: 58918 Version: 11.2 Status: Open defect, requires resolution Description: There is a memory leak when DLL are dynamically loading and unloading when the Dialogs or Controls units are in uses. This a critical bug when the DLL is used by a windows ...

• dbxmss30.dll appears to have a memory leak QC#: 59293 Version: 11.2 Status: Open defect, requires resolution Description: When using a TClientDataSet to connect to MS SQL Server, a memory leak occurs. Using the Windows Task Manager the working set increases indefintely for each query. 11.0.290 ...

Next: JetBrains' Dmitry Jemerov on IntelliJ 8, Flex, and Scala