Hostinger cuts server response times by up to 35% without expanding infrastructure

Hostinger has reduced server reply times by up to 35% following optimizing its in-house satisfied shipment network (CDN). The improvements made the CDN productive adequate to rotate it out throughout all web hosting plans, including Premium and Single, at no additional cost.

“By making our CDN additional productive under the hood, we can now provision all client a faster, additional resilient location without asking them to pay for additional infrastructure costs. That’s the benevolent of betterment that have to be standard,” stated Saulius Lazaravičius, Chief Product Officer at Hostinger.

After completing the CDN optimization, Hostinger automatically migrated existing web hosting customers who met three conditions: they used Hostinger DNS, weren’t already operating another CDN, and hadn’t opted out of the rollout. New web hosting customers now have the Hostinger CDN enabled by default.

Following the rollout, first infrastructure-wide data display that average reply times cut by 26%, from 965 ms to 714 ms. The achievement gains were most notable on SSD-based web hosting servers, anywhere average reply times improved by 35%.

SSD servers had small achievement headroom than newer NVMe-based infrastructure, so reducing backend burden led to a larger betterment in reply times. Although they now create up lone a smaller group of Hostinger’s fleet, SSD-based servers saw the biggest gains from the optimization.

The betterment was driven in part by small force on the lower-tier web hosting servers. These servers used to run at 20–30% complete the average burden of Hostinger’s Business and Cloud infrastructure. Following the rollout, the trend reversed, alongside Premium and Single web hosting servers operating at 15–20% below that average.

The benefits extended beyond websites that use the Hostinger CDN. By reducing general server pressure, equal websites without the CDN enabled achieved faster reply times.

Rather than adding new servers or hardware, the business reduced the computing resources needed to run its CDN by 45–50%.

A key part of that attempt was making encrypted connections additional efficient. Hostinger migrated SSL certificates from RSA to ECDSA, reducing CPU use for SSL-related operations to approximately one-third of its former level.

The business additionally adopted kernel Transport Layer Security (kTLS) and improved meeting resumption, additional reducing the resources needed to assist returning visitors.

Another important acquire came from Hostinger’s in-house traffic engine. Instead of multiple regions independently fetching and handling the identical content, requests can be routed through the border closest to the website’s base using warm, pooled connections.

This cut association setup times from tens of milliseconds to about 3 ms and reduced earth CPU use by about 20%. Processing tasks, specified as depiction optimization, can additionally be reused throughout the network fairly than repeated in multiple locations.

Other smaller engineering improvements contributed to the remaining gains, including eliminating inner fastener contention, moving bot fingerprinting into native code, and streamlining storage, logging, petition handling, and border procedure recovery.

These optimizations made it imaginable to recommendation the CDN throughout all of Hostinger’s web hosting plans fairly than reserving it for higher-priced plans as before. The CDN rollout is now completed throughout all of Hostinger’s web hosting plans at no additional cost.