Re: IBM article on Java performance

[Peter Ammon <gershwin@xxxxxxxxxxxxxxx>]
|
| Thoughts?

malloc() and memory allocation in Java doesn't even resemble each
other so I can't really understand how optimizations possible for one
is relevant to the other.

for one malloc()'ed objects cannot be moved on subsequent invocations
of malloc() or free(). in Java you have no such restriction.

-Bjørn
.

Relevant Pages

  • Re: OO compilers and efficiency
    ... >>> performance is due to Java implementations failing to optimise common OO ... > single good language designer. ... >> situations where a GC would outperform manual allocation though. ... >> Yes, that's true, but malloc and free are generally very efficient. ...
    (comp.programming)
  • C++ vs Java "new" (no flame war please!)
    ... Do not take anything about this, it is not a flame or troll, while I'm not ... memory overhead of malloc. ... but if you have 10 or 100 million objects, the malloc block overhead, ... Is there a way to create 10 to 100 million objects in Java with a reasonable ...
    (comp.lang.java)
  • Re: Java outperforms C++?
    ... It's true that managed versus unmanaged code does not mean respectively slow ... Ever thought of the things "malloc" does before returning ... Ofcourse, if you are an experienced coder, you have created memory pool ... they compare recursive C++ functions with iterative Java calls? ...
    (microsoft.public.vc.language)
  • Re: Good books for a complete beginner!
    ... And actually I believe Monique is a boys' name. ... Java and javascript are different. ... finally saw a malloc() for the first time instead of a new. ...
    (comp.lang.java.help)
  • Re: A question related to type casting
    ... "List.class" from the overridden method is "final"), how would that returned instance properly reflect on an instance of "__specialised_List"? ... The unfortunate part is that both he and I are falling back on using Java code to try to illustrate something that's not really Java code. ... My whole point from the beginning was with respect to the _general_ case of how the non-reifiable nature of Java generics limits how efficient a generic class can be. ... In other words, in spite of the _potential_ for some specific optimizations, there is a basic and fundamental limitation in generics just as I described at the outset. ...
    (comp.lang.java.programmer)