Slashdot Mirror
Java Performance Urban Legends
An anonymous reader writes "Urban legends are kind of like mind viruses; even though we know they are probably not true, we often can't resist the urge to retell them (and thus infect other gullible "hosts") because they make for such good storytelling. Most urban legends have some basis in fact, which only makes them harder to stamp out. Unfortunately, many pointers and tips about Java performance tuning are a lot like urban legends -- someone, somewhere, passes on a "tip" that has (or had) some basis in fact, but through its continued retelling, has lost what truth it once contained. This article examines some of these urban performance legends and sets the record straight."
There was this one guy who worked for Sun Micro and was disappointed at how slowly Java ran on his Sparcstation, so he attached one of those JATO rocket engines...
k.
"In spite of everything, I still believe that people are really good at heart." - Anne Frank
Ok, so none of the things we thought were slow are really slow.
Then why the hell is it so slow?
Save optimizations for situations where performance improvements are actually needed, and employ optimizations that will make a measurable difference."
1) become a journalist
2) use common sense and lots of bullshit
3)????
4) profit!
The missing step appears to be get an MBA and go into management
I'm not Seth.
sigh, I can't believe I misspelled it twice
No, you didn't. You misspelled it once; the second time is simply being consistent.
Misspelling it twice would be writing "optomizing" and "optomezing"
It must be all these Java "programmers" that University CS departments world wide keep churning out that couldn't write a well performing program if their life depended on it?
*looks at Limewire*
*looks at administration applets written by Sun which don't work over X11*
"Java Performance Urban Legends" should read "Java Performance is an Urban Legend".
Tarsnap: Online backups for the truly paranoid
don't you understand... there is a Special Case where it will start something up fast... if it's already been started up... so if you start the app 3 times... you have a 66% startup time improvement! you have to study these things closely. Also, VMs can run as fast as compiled code, after all, they are compiled code, but they just won't run your Java code as fast. I mean, the java code can run just as fast, as long as your JVM is optimizing on the fly based on dynamic code profiling... of course, it won't seem faster because the dynamic profiling and recompiling is expensive, but the original code is running faster!
Slashdot Journal on Monopoly News
It was somewhat shocking to me, but back in the VAX days I learned that software made by hardware manufacturers is as slow as they can get the customer to accept. That makes customers buy more hardware.
Following the theme of naming products after food items, Sun's next software product is "Molasses".
If customers accept Molasses, the next January they will release an upgrade called "Molasses in January". The following product will break the naming tradition: It will be a run-anywhere language called "The check is in the mail". After that, there is "When pigs fly", and "When hell freezes".
The big question in the computing world is how not to become a dog on some manufacturer's leash. Woof, woof, where do you want me to go today, Bill, Steve, or Scott?
Or, perhaps you're just a moron who just can't spell reasonabl well at all....
because Eclipse is based on SWT not Swing.
Swing = Sick WINdowing Garbage