everything there is to know about the jvm...
i've coded quite a few successful production server-side java apps over the past 10 years.
i have (in my opinion) adequate knowledge of the jvm for what i am most often hired to do as a humble application developer. i know the difference between the stack and the heap; i know when to tweak the min/max heap size; i know there are different areas of the heap (for new objects and old objects, etc); i know there is a limitation on the amount of physical memory available to the jvm on 32bit wintel architectures; i've ran javap -c on one or two classes to peek at bytecode (just out of curiousity more than anything); i know that a single java source code statement is compiled into more than one line of bytecode instructions, and the implications that has on multithreaded apps, etc.).
i've gotten by just fine in my career as a java developer without having to delve too deeply into the inner workings of the jvm. please, can anybody here answer this for me:
what would i gain by learning more about the inner workings of the jvm than "the basics" which i already know? i mean apart from gaining the ability to impress ubergeeks who care about that kind of arcane stuff ;?
personally, i think my brain's cycles can be put to better use by spending time on something other than learning everything there is to know about the jvm. can anybody here convince me otherwise?
many thanks,
sun_certified
