Add a comment

 

Re: JVM Lies: The OutOfMemory Myth

Another resource you need to consider is virtual address space. As mentioned, under 32bit Windows, this is typically 1.7gigs or so. Using memory maps from Java effectively consumes "native virtual address space" outside the JVM's heap (created via FileInputStream.getChannel().map()), so you can end up with nasty "native" OOM errors (out of "swap space") as a result if you are not careful.

Re: JVM Lies: The OutOfMemory Myth


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).