February 2, 2012
0 Comments
To give you an estimate of how many memory related resources you will need to run a Java application server or a Java application within Java Virtual Machine we tested some popular ones and are publishing results below.
(Full Story: JVM Host – Memory usage comparison of Java Application Servers and Applications)
February 1, 2012
0 Comments
A presentation by Attila Szegedi titled “Everything I Ever Learned about JVM Performance Tuning @twitter” has been floating around for a few months. I’ve restructured much of the content into a set of notes. This covers the basics of memory allocation and garbage collection in Java, the different garbage collectors available in HotSpot and how they can be tuned, and finally some anecdotes from Attila’s experiences at Twitter.
(Full Story: JVM Performance Tuning (notes) : twitter)
December 12, 2011
0 Comments
Gil Tene explains the workings of a garbage collector: terminology, metrics, fundamentals, key mechanisms, classification of current GCs, the “Application Memory Wall” problem, and details Azul C4 GC.
(Full Story: InfoQ: Understanding Java Garbage Collection and What You Can Do about It)
November 30, 2011
0 Comments
Java Performance, Java Concurrency in Practice, etc
(Full Story: A reading list for JVM-based developers)
November 26, 2011
0 Comments
May 19, 2011
0 Comments
JRockit is now free (gratis) for development and internal production use on general purpose computers. Commercial features continue to require a commercial license.
(Full Story: JRockit is Now Free and Other Java License Updates)
May 10, 2011
0 Comments
The Dynamic Code Evolution Virtual Machine (DCE VM) is a modification of the Java HotSpot(TM) VM that allows unlimited redefinition of loaded classes at runtime. The current hotswapping mechanism of the HotSpot(TM) VM allows only changing method bodies. Our enhanced VM allows adding and removing fields and methods as well as changes to the super types of a class.
(Full Story: Dynamic Code Evolution JVM)
April 13, 2011
0 Comments
According to the slides, the Ceylon Project aims to create a programming language and SDK for business computing, designed with an eye to the successes and failures of the Java. It is built to run on the JVM, uses static typing, and supports high-order functions, while maintaining a strong focus on being easy learn and easy to read.
(Full Story: Gavin King unveils Red Hat’s top secret Java Killer/Successor: The Ceylon Project)
April 7, 2011
0 Comments
Choosing a Framework:
1. Developer Productivity
2. Developer Perception
3. Learning Curve
4. Project Health
5. Developer Availability
6. Job Trends
7. Templating
8. Components
9. Ajax
10. Plugins or Add-Ons
11. Scalability
12. Testing Support
13. i18n and l10n
14. Validation
15. Multi-language Support (Groovy / Scala)
16. Quality of Documentation/Tutorials
17. Books Published
18. REST Support (client and server)
19. Mobile / iPhone Support
20. Degree of Risk
(Full Story: Matt Raible’s – Comparing JVM Frameworks (April 2011 updarte))
