Java abstracts away from many technical details. To get high-speed code execution, it heavily relies on JIT compilation in JVM. JIT compilation improves the performance of Java applications by compiling Java bytecodes to native machine code at run time. The cost model differs from static/AOT compilation and to produce performant code JVM needs to use a different set of techniques. The talk will cover JIT compilation techniques in general and JIT compilation peculiarities for Java. Overview of JIT compilation framework in HotSpot JVM will include best practices on how to look “under the hood” (down to assembly code) of your Java application and diagnose performance problems.
The latest expert opinions, articles, and guides for the Java professional.
Those teams that replied ‘Often’ or ‘All the time’ to this question are just barely breaching the 40% level. However, ‘Sometimes’ is the largest single group at 47%–although like quality assurance, solving technical debt isn’t a one-time thing, it’s a constant exercise that needs to be incorporated in every release. Like people who only exercise or work out “sometimes”, the greatest benefits are witnessed by those who do it very frequently. In this group, 12% of teams either rarely or never work on reducing technical debt. So, we can see that 6 out of 10 teams consider technical debt a non-priority. That is, until the sky starts falling ;-)
Early results from our ongoing Developer Productivity Report survey have shown us that a large amount of app releases often contain critical bugs. Oh no! Here’s a sneak peak at some of the answers we recorded when asking developers about software quality:
Code quality who? Over half of dev teams surveyed (53%) don’t fix and/or don’t monitor the code quality of their apps (e.g. using Sonar). The rest fix at least some code quality problems.
Not so much automation-foo: A large minority (43%) of teams do not automate testing of their app, and only about 1 in 5 teams makes it a priority.
Buggy apps for you! Bugs that block functionality go into releases at least ‘sometimes’ for 60% of development teams, and this doesn’t include non-critical issues.
One of the key benefits of continuous integration servers is to be able to effectively utilize a large number of virtual computers, as they are becoming cheaper and more abundant. Doing this is becoming increasingly important as the expanding computing power clearly comes in the form of higher parallelism, not a faster computer.
In this talk, we first look at the basics of setting up Jenkins for a large number of slaves, then look at various techniques enabled by them, such as parallel testing, load testing with many load generating clients, and how to orchestrate those activities. I’ll highlight various plugins in Jenkins that are useful for this goal, and how they can be combined so that you can do the same on your Jenkins.
Rapid Growth Thanks to Award-Winning Java Productivity Tool
Boston – August 21, 2013 – ZeroTurnaround, the company that’s helping software eat the world faster, announced today that the company is saving Java developers millions of productive hours annually. Within the past 365 days, ZeroTurnaround’s award-winning JRebel solution has saved developers 8,370,000 hours (or about 955 years) by eliminating approximately 162,000,000 Java application server restarts (redeploys).
A DevOps Vision with GitHub, Artifactory, Bamboo, Arquillian, Selenium and LiveRebel
“Mastering Release Management using tools like GitHub, Artifactory, Bamboo, Selenium, Arquillian and LiveRebel ensure an automated deployment pipeline that can bring your organization into the mental area of DevOps and on the road to seamless Continuous Delivery.”
Spring has a track record of providing dedicated support for new Java generations in a timely fashion, and now it’s right about time to go Java 8: With Spring Framework 4.0, we’re providing in-depth support for all relevant OpenJDK 8 features, including lambda expressions, JSR-310 Date and Time, parameter name discovery, and
java.util.concurrent enhancements. This talk will illustrate selected Java 8 features within Spring’s programming model and explore the impact on application architectures.
If you haven’t seen our popular Java Web Frameworks report well… this is the time to do it! As you can imagine, there is some controversy surround the opinionated report that compares Spring MVC, Grails, Vaadin, GWT, Wicket, Play, Struts and JSF together based on 8 functional areas, which ZeroTurnaround Founders Jevgeni and Toomas debate with great fury…