What unites VDS, Ruby and 1C-Bitrix: Corp. Portal? Jelastic on Infobox

Two weeks have passed since we launched the new cloud platform Jelastic. Today we want to share news about its improvement.

We will talk about the creation and use of VDS on Jelastic, about the beginning of Ruby support, about how we tested the new installation package for deployment on Jelastic “1C-Bitrix: Corporate Portal”, and how much hosting for this product will cost.


')

VDS on Jelastic

To begin with, we added the ability to use VDS during beta testing. This service is included in the basic Jelastic functionality, but has not yet been offered by any provider during beta testing. Upon request, we provide this feature, while free of charge we allocate an external IP address for the beta period. We remind you that beta testing will last until October 15.

VDS allows you to significantly expand the range of tasks that can be solved on Jelastic. For example, it can host a database that requires specific modules, such as PostGIS, or install a web server with Python support. In general, you can everything that you did not have before. At the same time, for VDS, similarly to other environment nodes, autoscaling works, and billing is carried out only for used claudlets (1 cloudlet = 200 MHz processor and 128 MB of RAM).



In addition to using VDS as part of the environment, there is a scenario for its standalone operation. In this case, an environment consisting only of VDS is created, and resource allocation is configured. Since 3 cloudboxes on Infobox are free ( we wrote about this in the first post about Jelastic), they can be set as a lower limit for autoscaling. Thus, you get a virtual dedicated server with a 600 MHz processor and 384 MB of RAM practically free of charge (only the hard disk is charged). And if you need to place a more loaded project, you simply raise the upper limit of autoscaling and pay for the keylates that are consumed in excess of 3 free ones.

Registration for beta on our site is here , and to activate VDS on your account you just need to write us an email at help @ infobox.ru.

Ruby support

The next innovation was support for Ruby. The possibility of using Ruby environments is announced as a test, but no problems were identified during testing.

Ruby is launched via an Apache web server with Passenger version 4.0.2 installed. In the near future we will write a separate article on working with CMS, working on Ruby.

What should we build a portal?

The latest news is the addition of 1C-Bitrix: Corporate Portal to the application catalog for auto-deployment in the “Collaboration” edition. We worked especially carefully on this application, since Jelastic, in our opinion, is the optimal platform for hosting corporate portals.
Judge for yourself: shared-hosting cannot be by definition a sufficiently reliable solution for hosting a corporate portal, so we will not take it into account. VPS and dedicated servers are quite complicated to configure and may also be more expensive.

With Jelastic, thanks to the possibility of installing CMS in 1 click, the portal can be installed in a few minutes. At the same time, you will receive a portal that will work in a well-optimized environment with high performance in the Beatrix performance monitor. As a result of tuning the web environment, which we produced in conjunction with Bitrix specialists, we achieved a performance of 45 units from the basic 7 units, which is very good for this rather demanding product.

As for the cost of hosting on Jelastic, not to be unfounded, we conducted tests under the load that can generate a small company of 25 employees. A corporate portal was deployed from the catalog, on which 25 users were created (the number of users included in the license of this edition).



After that, using Xenu, we got links to all elements of the site (pages, css, js, images) and exported the result to a text file. The advantage of Xenu is that it provides links to objects in exactly the order in which they are downloaded by the browser when the site loads, so when they are loaded sequentially, we get a more or less realistic imitation of the resource load.

The resulting text file is divided into blocks. Each block will begin with a link to the page and end with the last element of the page (in fact, we searched for the end of the block at the beginning of the next :)). Then we shuffle the blocks together and save 25 copies of this file with the blocks going in a different order.

We now turn to testing directly.
25 VPS on CentOS, for each of which we installed siege and launched it with the following parameters:
- from 1 - each copy of siege imitates an individual employee, therefore 1;
-t60M - we test within one hour;
-f /home/links.txt - the path to the previously created file with links;
-H "Cookie: PHPSESSID = ntsgqk37lod6cauga70jd0tr03; BITRIX_SM_LOGIN = admin; ... "- we record the user's cookies;

As a result, we get a rather realistic load of active work simultaneously of all users with the portal.





The graph shows that the maximum number of Apache claudlets involved is 7 (1 cloudlet is 200 MHz). Let's add to this 1 Nginx cloudlet and 3 MySQL cloudlets (their number was constant throughout the entire test). Total we get - 11 klaudletov. Minus 3 free cloudlet - already 8.
MySQL consumes 2 cloudloads without a load, so it makes sense to put them static, that is, one of the 8 paid cloudlet turns out to be static, which means cheaper.
1 Static claudlet 0.25 rub. + 7 dynamic claudlets for 0.35 rubles. = 2.7 rubles per hour.

Suppose that our employees are active and use the portal 12 hours a day, the day costs 12 * 2.7 = 32.4 rubles. At night, without load, the environment will consume 4 clouds, of which MySQL reserves 2 clouds, that is, 1 static will be paid. 0.25 * 12 = 3 rubles. Total 35.4 rubles per day.
35.4 * 30 = 1062 rubles a month of operation of the portal + disk space of 25 rubles per month for 1 GB.

Compare with the recommended hosts in the list on the developer's site . We will look at offers from a CPU of 2000 MHz and RAM of 1280 MB (which is even slightly less than necessary), recommended for hosting a corporate portal.
The most advantageous offer that was found - 1800 rubles per month. This is excluding administration and deployment costs. And during the deployment will require more resources than in normal operation.
These are the results of testing and hosting cost calculations.

Information about the service and registration for beta testing on our website .