InfoboxCloud Cloud Platform Update: Jelastic 1.9.3

    The InfoboxCloud Jelastic Cloud Platform will be updated soon to version 1.9.3. The Jelastic platform in InfoboxCloud allows you to get Java, PHP and Ruby environments, the necessary SQL and NoSQL databases, cache, VDS and more in 1 click.

    In this case, the user does not fall into absolute dependence on the platform provider. You can configure all the same applications on other servers, just in Jelastic this process is automated and you do not waste time setting up and maintaining the infrastructure, getting the necessary components for your software and services to work - save money.

    In addition, a really working autoscale allows you to use as many resources as the application needs at a particular point in time and not pay for the potentially possible maximum resources needed.

    In this article we will look at what the InfoboxCloud Jelastic Cloud Platform update is preparing for us .
    InfoboxCloud Jelastic

    Scalability and performance improvements


    Java

    Jelastic gc agent

    Garbage Collection (GC) - a type of automatic memory management. The garbage collector tries to clear the memory occupied by objects that will no longer be used by the executable program. As a result, the cost is reduced due to the release of unused resources.

    The Jelastic platform uses a special Garbage Collector agent along with the standard Java Virtual Machine garbage collectors.

    Jelastic GC agent is enabled by default for all newly created Java application servers.

    It works with only two types of GC:

    -XX: + UseParNewGC (if -Xmx <8000m)
    -XX: + UseG1GC (if -Xmx> = 8000m)

    These settings can be changed, but if you select another garbage collector manually, it will not be available call full GC.

    By default, the garbage collection process will be performed every 15 minutes (starting from the start of the JVM) to free up unused memory. The launch period can be changed depending on your requirements. You can also switch to debug mode.

    -javaagent: /var/lib/jelastic/java/jelastic-gc-agent.jar=debug=true,period=900

    This solution is unique and originally developed by Jelastic engineers to improve memory management of your application and as a result to reduce memory consumption.

    Php

    1. Zend OPcache

    Zend OPcache is now enabled by default and as a result, performance increases up to 40%. Zend OPcache speeds up PHP execution through opcode caching and optimizations.

    Apache and Nginx (php 5.3, 5.4, 5.5) include the OPcache extension enabled through etc> php.ini:

    zend_extension = / usr / lib64 / php / modules / opcache.so

    Cache size and other OPcache settings can be configured via php.ini by changing the following parameters:

    • opcache.enable = 1
      enable / disable the OPcache extension


    • opcache.memory_consumption = 64
      setting the size of used RAM


    • opcache.interned_strings_buffer = 8
      size of used RAM for storing internal strings (for example classnames)


    • opcache.max_accelerated_files = 4000
      maximum number of cached files


    • opcache.revalidate_freq = 60
      frequency of checking files by change time


    • opcache.fast_shutdown = 1
      enable / disable fast completion of an accelerated code sequence Fast completion of a sequence does not release every selected block, but it allows Zend Engine Memory Management to do its job.


    • opcache.enable_cli = 1
      enable / disable OPcache for CLI version of PHP


    More detailed information

    2. Automatic change in the number of workers

    The number of workers processing PHP requests automatically increases on the Apache server, depending on the number of cloudlets allocated.

    To test this feature, click Config on your Apache web server and go to conf> httpd.conf .

    Find and remember the value of Max clients. After that, change the topology of your environment by increasing or decreasing the limit of cloudlets on your server.

    Go back to conf> httpd.conf . You will see that the value of Max Clients has been increased / decreased.

    Note that this feature will be disabled if you remove the following line from the httpd.conf file:
    # Jelastic autoconfiguration mark

    3. Manual mod_security settings

    mod_security - Apache module that provides the ability to easily filter, check URLs and Unicode, audit, prevent null byte attack ; limits the size of the downloaded data, masks the details of the functioning of the server, etc.

    This module is available in Jelastic by default and can be configured through conf.d> mod_security.conf .

    In this file you can edit the default configuration or add your own settings.

    For example, you can add additional ModSecurity rules. To do this, you just need to upload your rules to the modsecurity.d folder. They will be automatically activated through the Include modsecurity.d / *. Conf line in conf.d> mod_security.conf.

    Database Improvements


    1. Editable MyAdmin-jel.conf, phpPgAdmin and couchdb.conf files

    Starting with this release, you have access to MyAdmin-jel.conf (for MariaDB and MySQL), phpPgAdmin (for PostgreSQL) and couchdb.conf (for CouchDB). These files are located in the conf.d folder .

    These files can be edited to set appropriate criteria for allowing / denying access by ip-address or domain for an application working with a database at the Apache web server level.

    2. Shooting processes to free memory

    When there is not enough RAM in your environment, processes with a high level of memory consumption are shot by the OOM killer to free resources. The procedure for disabling processes is specified in the OOM settings.

    Now oom_score_adj is used to shoot the least important processes (httpd) and only last but not least the database processes (mysql).

    3. Backup of several MongoDB databases

    Making backups is very important at any stage of the development process, guaranteeing the security and integrity of your data. Jelastic allows you to plan database backups and you can always restore the latest copy of your information in case of data loss. To do this, we provide a special script for database backups that can be customized to suit your requirements.

    In this release, we have improved the MongoDB database backup script. Now you can use it to backup multiple databases. Just specify the necessary settings as described in the MongoDB database backup instructions .

    4. Changes to the default database configuration
    In this release, the following database default settings have been changed in php.ini:

    upload_max_size = 1024MB
    post_max_size = 1024MB
    max_execution_time = 600
    max_input_time = 600

    This is a consequence of the ability to load large dumps. These changes are introduced for all new and previously created containers, with the exception of containers that you manually configured.

    HTTP Transport Error


    When you perform any actions in the Jelastic control panel (for example, creating environments, deploying applications, building a project, reloading the application, etc.), you may encounter an HTTP Transport Error problem that occurs with some problems with the Internet connection. As a result of the disconnection, your actions completely stopped and you had to start all over again.

    Now this situation is radically improved. When the connection is broken, it simply falls asleep to the process that you initiated earlier and continues when the connection is restored. After that, the last request will be resumed and the process completed without the need for additional configuration of anything.

    Other improvements


    The display of the billing history has been updated - it has become clearer.

    Now, when saving configuration files in Jelastic, the option “Do not show the save confirmation dialog again” appeared. If you check this box, configuration files will be saved automatically. Settings apply to all types of configuration files for all environments.

    Software Stack Versions in Jelastic 1.9.3


    Tomcat 6 6.0.37
    Tomcat 7 7.0.47
    TomEE 1.5.2
    Jetty 6 6.1.26
    GlassFish 3 3.1.2.2
    Java 6 1.6.0_45
    Java 7 1.7.0_45
    MariaDB 5.5.34 / 10.0.6
    MongoDB 2.4.8
    MySQL 5.5.34
    PostgreSQL 8 8.4.18
    PostgreSQL 9 9.3.1
    CouchDB 1.5.0
    nginx 1.4.3
    Maven 3.0.5
    Centos 6 6.4
    Memcached 1.4.15
    Apache 2.2.15-29
    NGINX PHP 1.4.3
    PHP 5.3 5.3.27
    PHP 5.4 5.4.21
    PHP 5.5 5.5.5

    Successful use of the InfoboxCloud Cloud Platform .

    Also popular now: