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

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

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



VDS on Jelastic


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

VDS allows you to significantly expand the range of tasks that can be solved on Jelastic. For example, you can place a database on it that requires specific modules, such as PostGIS, or install a web server with Python support. In general, you can do everything that you lacked before. At the same time, for VDS, similarly to other environment nodes, autoscaling works, and charging is carried out only for used cloudlets (1 cloudlet = 200 MHz of the 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 of only VDS is created, and resource allocation is configured. Since 3 Cloudletts on Infobox are free ( we wrote about this in the first post about Jelastic), they can be set as the lower limit of autoscaling. Thus, you get a virtual dedicated server with a 600 MHz processor and 384 MB of RAM almost free (only a hard drive is paid). And if you need to place a more loaded project, you simply raise the upper limit for autoscaling and pay for cloudlet consumed in excess of 3 free ones.

Registration for beta on our website 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 ability to use Ruby environments is announced as a test, but no problems were found during testing.

Ruby is launched through the 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 catalog of applications for auto-deployment in the collaboration team. We especially carefully worked on this particular application, since Jelastic, in our opinion, is the optimal platform for hosting corporate portals.
Judge for yourselves: shared hosting cannot be, by definition, a reliable enough solution for hosting a corporate portal, so we won’t take it into account. VPS and dedicated servers are quite complicated to set up and can also be more expensive.

With Jelastic, thanks to the ability to install CMS in 1 click, the portal can be installed in a few minutes. At the same time, you will get a portal that will work in a well-optimized environment with high performance in the Bitrix performance monitor. As a result of tuning the web environment, which we performed together with Bitrix specialists, from the base 7 units we came to a performance of 45 units, which is very good for this product that is quite resource-demanding.

As for the cost of hosting on Jelastic, in order not to be unfounded, we conducted testing under the load that a small company of 25 employees can generate. 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 the exact 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 simulation of the resource loading.

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 looked for the end of the block at the beginning of the next :)). Then we mix the blocks together and save 25 copies of this file with blocks going in different order.

Now we will pass to testing directly.
25 VPS on CentOS, on each of which we installed siege and launched it with the following parameters:
-c 1 - each instance of siege imitates a separate employee, therefore 1;
-t60M - test for one hour;
-f /home/links.txt - path to a previously created file with links;
-H "Cookie: PHPSESSID = ntsgqk37lod6cauga70jd0tr03; BITRIX_SM_LOGIN = admin; ... "- write the user's cookies;

As a result, we get a fairly realistic load of active work at the same time for all users with the portal.





The graph shows that the maximum number of involved Apache cloudlets is 7 (1 cloudlet is 200 MHz). Add to this 1 Nginx cloudlet and 3 MySQL cloudletts (their number was constant throughout the test). Total we get - 11 cloudlets. Minus 3 free cloudlets is already 8.
MySQL consumes 2 cloudlets without load, so it makes sense to set them static, that is, one of the 8 paid cloudlets turns out to be static, which means cheaper.
1 Static cloudlet at 0.25 rubles. + 7 dynamic cloudlets at 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 cloudlets, of which MySQL reserves 2 cloudlets, 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 functioning of the portal + disk space of 25 rubles per month for 1 GB.

Compare with the recommended hosters in the list on the developer's site . We will look at offers with a CPU from 2000 MHz and RAM from 1280 MB (which is even a little less than necessary), Recommended for hosting a corporate portal.
The most advantageous offer that was found was 1800 rubles per month. This excludes administration and deployment costs. And the deployment will require more resources than during regular work.
Here we have the results of testing and calculations of the cost of hosting.

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