October 19, 2015 By Jarek Gawor 2 min read

Performance improvements in Liberty buildpack v2.1

Today, we have released a new version of the Liberty buildpack. The v2.1 buildpack provides a couple of important performance improvements:

 

  • App Management utilities: In June, we introduced an enhanced app management support: a collection of utilities that provide development and debug functionality to Liberty applications running in Bluemix. Two of those utilities – devconsole and shell – provide a nice web-based interface. The web interfaces pull in a large of set of dependencies that consume a lot of disk space and can take a while to install and start. In the new buildpack, we have optimized the devconsole and shellutilities to reduce the disk, install and start time overhead. With these optimizations, we also have reduced the droplet size and decreased the overall time it takes to deploy a Liberty application to Bluemix!
    In order to maximize these improvements, the shell and devconsole utilities now require a restageoperation instead of restart to enable them. For example, to enable both utilities for your application execute:

    <br>
    $ cf se myApp BLUEMIX_APP_MGMT_ENABLE devconsole+shell<br>
    $ cf restage myApp<br>

    Refer to the App Management documentation for further details.

  • CDI 1.2 annotation scanning: By default, when deploying a WAR or EAR file to Bluemix, the buildpack will automatically enable Java EE 7 Web Profile Liberty features for the application. One of those features is cdi-1.2 feature. The Contexts and Dependency Injection 1.1/1.2 specification introduced the concept of implicit bean archives – archives that are without the beans.xml file and contain CDI annotated classes. With the cdi-1.2 feature enabled, such archives must be scanned for annotations. In case of large applications with a number of library files, the annotation scanning can take a long time to complete and significantly increase the application start up time. For this reason, the annotation scanning of the implicit archives is disabled by default for WAR and EAR files. If needed, the implicit bean archive scanning can be enabled for an application using the JBP_CONFIG_LIBERTY environment variable. For example:

    <br>
    $ cf se myApp JBP_CONFIG_LIBERTY "app_archive: { implicit_cdi: true }"<br>
    $ cf restage myApp<br>

In addition to the performance improvements, the buildpack contains an updated version of Liberty profile based on the October beta. With this update, the bells-1.0rtcomm-1.0rtcommGateway-1.0samlWeb-2.0, and sipServlet-1.1 Liberty features, previously available as beta features, are now available as production-ready features. The buildpack also has an updated IBM JRE 8 SR1 FP11.

Reminder

If your application is deployed with the liberty-for-java-v1 buildpack, please make sure to move to the new v2 buildpack as the v1 buildpack will be deleted soon.

More from

How to establish lineage transparency for your machine learning initiatives

3 min read - Machine learning (ML) has become a critical component of many organizations' digital transformation strategy. From predicting customer behavior to optimizing business processes, ML algorithms are increasingly being used to make decisions that impact business outcomes. Have you ever wondered how these algorithms arrive at their conclusions? The answer lies in the data used to train these models and how that data is derived. In this blog post, we will explore the importance of lineage transparency for machine learning data sets…

How will quantum impact the biotech industry?

5 min read - The physics of atoms and the technology behind treating disease might sound like disparate fields. However, in the past few decades, advances in artificial intelligence, sensing, simulation and more have driven enormous impacts within the biotech industry. Quantum computing provides an opportunity to extend these advancements with computational speedups and/or accuracy in each of those areas. Now is the time for enterprises, commercial organizations and research institutions to begin exploring how to use quantum to solve problems in their respective domains. As a Partner in IBM’s Quantum practice, I've had the pleasure of working…

The history of the central processing unit (CPU)

10 min read - The central processing unit (CPU) is the computer’s brain. It handles the assignment and processing of tasks, in addition to functions that make a computer run. There’s no way to overstate the importance of the CPU to computing. Virtually all computer systems contain, at the least, some type of basic CPU. Regardless of whether they’re used in personal computers (PCs), laptops, tablets, smartphones or even in supercomputers whose output is so strong it must be measured in floating-point operations per…

IBM Newsletters

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.
Subscribe now More newsletters