Re: Out-of-Memory Handling in Long-Running / Server Applications
Attila Szegedi <[email protected]> Mon, 14 Apr 2008 22:38:40 +0200
| Newsgroups | gmane.comp.windows.devel.java.advanced |
|---|---|
| Message-ID | <[email protected]> |
On 2008.04.14., at 22:08, Randall R Schulz wrote: > On Monday 14 April 2008 13:01, Bob Lee wrote: >> Compared to allocating a >> really huge heap (bigger than physical RAM), you could gain some more >> control over when swapping out to disk occurs, but whether or not you >> could do a significantly better job than the OS's default algorithm >> is debatable. > > The access patterns are such that to achieve anything near acceptable > performance, the tree and the priority queue must remain in the > working > set. You could look into Terracotta. While it's primarily a JVM clustering solution, almost as a side-effect it gives you a >4GB disk backed virtual heap where your RAM based heap basically serves as a cache. Attila. =================================== This list is hosted by DevelopMentorĀ® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com