Building Memory-efficient Java Applications
domino.research.ibm.com
Building Memory-efficient Java Applications
1–10 of 16 posts
Re: Building Memory-efficient Java Applications
#2Cool! Very good explanations.
Re: Building Memory-efficient Java Applications
#3Very nice presentation. However much of this can be actually discovered and felt first hand just by playing with profilers that support memory profiling (such as yourkit[1]).
After a few hours playing with it, you will never forget the precious lessons on this presentation.
Re: Building Memory-efficient Java Applications
#4Does anyone know of a similar study of memory efficiency in C# (or the CLR in general)?
Re: Building Memory-efficient Java Applications
#5TreeMap, 100 entries, 8.6 kB, 82% overhead
Man, that's just annoying.
Re: Building Memory-efficient Java Applications
#6This is probably an 'apple and oranges' type of question, but I haven't used Erlang, nor Java to build large applications.
Does anyone know how Erlang compares to Java in regards to memory usage/performance?
Re: Building Memory-efficient Java Applications
#7This is probably an 'apple and oranges' type of question, but I haven't used Erlang, nor Java to build large applications. Does anyone know how Erlang compares to Java in regards to memory usage/performance?
Per-object overhead is generally more reasonable.
Re: Building Memory-efficient Java Applications
#8This is probably an 'apple and oranges' type of question, but I haven't used Erlang, nor Java to build large applications. Does anyone know how Erlang compares to Java in regards to memory usage/performance?
You can have a whole Erlang process for a price of (roughly) 100 Java objects.
Re: Building Memory-efficient Java Applications
#9It just goes to show that whatever language you use, you need to understand what the abstractions are doing: what bytes are really going where?
Re: Building Memory-efficient Java Applications
#10This is probably an 'apple and oranges' type of question, but I haven't used Erlang, nor Java to build large applications. Does anyone know how Erlang compares to Java in regards to memory usage/performance?
Per object overhead in functional languages is usually lower since polymorphism is handled at the function level rather than the data level. You don't have to store class pointers etc, just the raw data and probably a type tag.
I can't find a reference for erlang's representation but I believe it has only a little more overhead than ocaml which is described here - http://rwmj.wordpress.com/2009/08/04/ocaml-internals/