Slashdot Mirror

← Back to Stories (view on slashdot.org)

Java Urban Performance Legends

Posted by ryuzaki0 on from the still-don't-like-java dept.

An anonymous reader writes "Programmers agonize over whether to allocate on the stack or on the heap. Some people think garbage collection will never be as efficient as direct memory management, and others feel it is easier to clean up a mess in one big batch than to pick up individual pieces of dust throughout the day. This article pokes some holes in the oft-repeated performance myth of slow allocation in JVMs."

3 of 846 comments (clear)

  1. Re:Duh Stack wins whats to agonize over? by dalleboy · · Score: 0, Flamebait

    Perhaps the web server is written in Java?

  2. Ok, the JVM allocation works by Orycterope · · Score: 1, Flamebait

    So, the JVM allocation works, and there's no performance bottleneck there. But where is it? Why is Java still so painfully slow?

    Java used anywhere, from webservers to full client apps just feels and even *looks* slow! Stop coming up with pointless articles. Find the problem and fix it.

    --
    Just because your voice reaches halfway around the world doesn't mean you are wiser than when it reached only to the end
  3. Re:Counter arguments by ctzan · · Score: 0, Flamebait
    While I'm sure you can point to a Java program which takes 5 minutes to start, these are the exception in the Java world, not the rule.
    Yes. here Java programs take only 3 minutes to start.