RESEARCH 》 Building my own CDN - choosing a web-hosting to deploy my CDN - Update: 28-July-2016

Yesterday I have done extensive study about which alternative web hosting service provider (or hosting provider) to choose. The TOFFEE Project website is hosted on Inmotion Hosting. And so I am looking for alternate hosting provider to build my first CDN node. My plan is to make multiple sub-domains of my website such as, and point each of this corresponding subdomain(s) to various alternative web hosting servers geographically spread across the world.

Sometimes choosing the same vendor for multiple CDN nodes may result multiple servers existing in the data-center. And this becomes an issue if there is some catastrophic network disaster. In such events not only your whole website may go down, but all its other associated CDN nodes may also fail to work. And this will affect your SEO and the end user experience. Which is why exactly I need to choose alternate hosting providers.

After extensive search I found Inmotionhosting have an option to choose your choice of Data-centre. I was extremely happy to find this option and shocked that when I initially subscribed during The TOFFEE Project website launch, I never much noticed this option. So I quickly confirmed via whoismyip look-up that the TOFFEE Project website is on a US west coast data-centre server. I cross checked the same with Inmotion's customer support team. I have also discussed about my agenda of building my own research private CDN with the Inmotion's technical customer support professional and got few directions how to proceed next with respect to website's sub-domain configuration(s) to deploy the same.

So far I never faced any issues with Inmotion Hosting and so I decided to subscribe (or purchase) a new web-hosting plan exclusively for my first CDN subdomain and choose a data centre situated in East coast. Here is my Inmotion Hosting AMP Customer Account management portal panel:
1 my Inmotionhosting AMP Portal Control Panel

You can choose ADD SERVICES -> HOSTING to get this below page. You can now choose which plan you wish to purchase. In this case I chose Business -> Launch plan.

2 Inmotionhosting AddServices Purchase new Hosting plan Business Launch

Here is the page in which you can see the Data Center option to choose either East or West (i.e US East Coast Inmotion Data Center or West Coast Data Center).
3 Inmotionhosting Purchase new hosting plan select data centre east coast or west coast

As one can understand the East Coast data center will be good at serving content faster to regions like EU, Africa, Middle-east and so on. Whereas the West coast data center will be good at server content to Australia, Japan, Korea, Russia, China, Indonesia and so on. Currently my idea is not to make 1:1 replica disaster recovery contingency sites. But instead build a network to address load-sharing, redundancy, and so on. May be in future I may write scripts to extend these features. But for now, I was part of my content served via West Coast data center server, and part via East coast data center server.

But in case in future if I wish to build another CDN node, then in that case I may choose to purchase a web hosting subscription(s) from Bluehost, Host Gator or some one else. Since at the moment there are only two physical data centers in which Inmotion Hosting is deployed. I may even opt for an European Hosting provider or choose a Web Hosting service provider who got their servers deployed in Europe. These days GoDaddy, Bluehost, Host Gator, etc have good Indian presence and business focused towards Indian customers. In that case building one of the CDN nodes on a server situated in an Indian Data Center is not a bad idea either. A server in India can easily cater users situated in Srilanka, Bangladesh, Singapore, Hong Kong, Korea, Malaysia, China, Middle East, Europe and Africa than a server in US to these regions.

When I do a lookup of existing TOFFEE project website IP (hosted on Inmotionhosting West coast Data center server) and do a traceroute I can see the packets are being routed from:

  1. My ISP Provider ACT Broadband Bangalore India -> VSNL Bangalore India
  2. VSNL Bangalore India -> VSNL Mumbai India (west coast of India connecting Middle-east, Europe, etc) -> Paris
  3. Paris -> (Level 3 Communications, California) -> (where the main website is hosted)
kiran@desktop-i7-5820k:~$ ping
PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=50 time=258 ms
64 bytes from ( icmp_seq=2 ttl=50 time=260 ms
--- ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 258.182/259.336/260.490/1.154 ms
kiran@desktop-i7-5820k:~$ traceroute
traceroute to (, 30 hops max, 60 byte packets
 1 (  1.838 ms  2.296 ms  2.823 ms
 2 (  21.223 ms  21.381 ms  21.448 ms
 3 (  21.732 ms  21.881 ms  21.991 ms
 4 (  22.209 ms  22.405 ms  22.534 ms
 5 (  22.759 ms  22.868 ms  23.026 ms
 6 (  23.799 ms  3.957 ms  22.269 ms
 7 (  22.471 ms 
(  22.686 ms (  22.907 ms
 8 (  23.836 ms  27.190 ms  27.294 ms
 9 (  29.271 ms  31.428 ms  34.467 ms
10 (  148.912 ms  149.721 ms 
(  151.971 ms
11 (  153.705 ms  155.361 ms  155.175 ms
12 (  137.402 ms  135.045 ms  134.989 ms
13 (  137.898 ms  138.948 ms  140.065 ms
14  * * *
15 (  275.698 ms  267.710 ms  265.135 ms
16  * * *
17  * * *
18  * * *
19 (  267.329 ms  266.286 ms  265.492 ms

4 Inmotionhosting geolocation of westcoast datacenter server

Now when I do a lookup of some random Inmotionhosting East coast Data center server ( and do a traceroute I can see the packets are being routed from:

  1. My ISP Provider ACT Broadband Bangalore India -> VSNL Bangalore India
  2. VSNL Bangalore India -> VSNL Mumbai India (west coast of India connecting Middle-east, Europe, etc) -> Paris
  3. Paris -> ( Level 3 Communications, New York)
  4. ->
kiran@desktop-i7-5820k:~$ ping
PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=44 time=212 ms
64 bytes from ( icmp_seq=2 ttl=44 time=212 ms
--- ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 212.712/212.714/212.716/0.002 ms
kiran@desktop-i7-5820k:~$ traceroute
traceroute to (, 30 hops max, 60 byte packets
 1 (  1.389 ms  1.933 ms  2.492 ms
 2 (  20.449 ms  20.560 ms  30.300 ms
 3 (  20.753 ms  20.934 ms  21.030 ms
 4 (  21.312 ms  21.397 ms  21.556 ms
 5 (  21.825 ms  22.538 ms  22.633 ms
 6 (  22.932 ms  3.653 ms  19.847 ms
 7 (  20.169 ms 
(  20.364 ms (  20.643 ms
 8  * (  22.755 ms  24.048 ms
 9 (  29.003 ms  29.813 ms  31.940 ms
10 (  146.773 ms  148.003 ms  149.098 ms
11 (  151.600 ms  134.586 ms  136.810 ms
12 (  135.878 ms  138.370 ms  138.476 ms
13 (  142.539 ms  142.862 ms  146.890 ms
14  * * *
15 (  223.095 ms  224.963 ms  225.363 ms
16  * * *
17  * * *
18 (  214.186 ms  215.119 ms  212.394 ms

5 Inmotionhosting geolocation of eastcoast datacenter server

With this analysis you can see the difference in the routing hops in-between both Inmotion servers and the associated ping round-trip latencies. In this case the advantage is not that significant, but yet you can notice its a valuable study to decide how you can architect and build your private CDN Network. Assume if you have more users in the Middle East, it makes more sense to host your CDN node in a good European data center or some trusted middle east data center. Make sure the data center you choose (location where it is situated) is immune to any political instability and communal clashes for obvious reasons and maximum up-time!

For now I may soon subscribe a new Inmotion Hosting web-hosting account (and choose West Coast Data Centre during its subscription/purchase) and going to setup my first CDN node. You can follow my previous updates about be same below.

RESEARCH :: Building my own CDN - Minify Script files - Update: 23-July-2016
RESEARCH :: Building my own CDN - Google PageSpeed Insights - Update: 22-July-2016

Here is my live video log of the same:

Suggested Topics:

Generic CDN

Building my own CDN

💎 TOFFEE-MOCHA new bootable ISO: Download
💎 TOFFEE Data-Center Big picture and Overview: Download PDF


TOFFEE-Mocha WAN Emulation software development - Update: 1-July-2016 ↗
Saturday' 13-Mar-2021
Today I got a feature request from Jonathan Withers. Jonathan is from a company called MultiWave Australia. He said he is able to get the TOFFEE-Mocha Raspberry Pi setup up and with that he is able to emulate geostationary satellite link. But he requested me is there a way to extend the constant packet delay from 40mS to 500mS. So as a part of his request I supported the same in the current ongoing development version of TOFFEE-Mocha.

Tweaking Network Latency - Live Demo - via TOFFEE-DataCenter ↗
Saturday' 13-Mar-2021

Recording Lab Monthly power-consumption readings for Research ↗
Saturday' 13-Mar-2021
Here is my home lab monthly power-consumption readings for research. This will help to measure and monitor the overall power usage and assess the power requirements. This will help me in future purchases such as UPS, battery upgrades and so on. And as well remove replace old obsolete hardware with new less power-consuming devices.

TOFFEE-DataCenter as a VNF for NFV ↗
Saturday' 13-Mar-2021

Off-Grid Home Lab Research Solar Installation ↗
Saturday' 13-Mar-2021

TOFFEE DataCenter WAN Optimization - Google Hangouts demo and VOIP Optimization ↗
Saturday' 13-Mar-2021
TOFFEE DataCenter WAN Optimization - Google Hangouts demo and VOIP Optimization

Raspberry Pi as a Networking Device ↗
Saturday' 13-Mar-2021
Raspberry Pi is often used as a single board computer for applications such as IoT, hobby projects, DIY, education aid, research and prototyping device. But apart from these applications Raspberry Pi can be used for real-world applications such as in making a full-fledged networking devices. Raspberry Pi is a single board ARM based hardware which is why it is also classified as ARM based SoC. Since it is ARM based it is highly efficient, tiny form-factor and lower in power consumption with moderate computational power. This will allow it to work several hours on emergency battery backup power supply such as low-cost domestic UPS and or some renewable energy source, which is a prerequisite for a typical networking device.

TOFFEE (and TOFFEE-DataCenter) deployment in Large Infrastructure and or ISP Networks ↗
Saturday' 13-Mar-2021
Large Infrastructure or ISP setup: In case if you are an ISP and interested in deploying a large customer WAN Optimized network or an add-on enhanced (WAN Optimized) network for select few customers, then you can deploy something as shown below. Although this case is not meant for hobby/DIY users. This is a feasible solution for high-end professional application and the same can be deployed.

TOFFEE-Mocha WAN Emulation software development - Update: 18-June-2016 ↗
Saturday' 13-Mar-2021
In the previous update (17-Jun-2016) I discussed about the upcoming new Random Packet drop feature along with other completed features. Now I completed the entire TOFFEE-Mocha Random packet drop feature. I completed all the kernel components and the UI support of the same. And to make GUI settings more organized I split the earlier Basic-Settings page into two separate pages namely: Packet Drop and Packet Delay. So this way it is simple to understand settings according to their functionality.

TCP Tune-up and Performance Analysis Graphs - Congestion Control - Research - Dos and Don'ts ↗
Saturday' 13-Mar-2021

Featured Educational Video:
Youtubeで見る - [8603//1] x254 Kernel Init Code without Kernel Module - Kernel Programming Tip #linode ↗

Internet optimization through TOFFEE-DataCenter WAN Optimization Demo ↗
Saturday' 13-Mar-2021
Internet optimization through TOFFEE-DataCenter WAN Optimization Demo

Skype VOIP Data - WAN Acceleration ↗
Saturday' 13-Mar-2021

CDN Hosting ↗
Saturday' 13-Mar-2021
It is quite interesting that there are few web hosting firms are offering direct CDN based hosting services. Since it is a direct CDN based hosting, it is cheap, extremely easy or transparent CDN service. It is transparent, since each time you publish your content in the hosting web-server (origin server), it is immediately is in sync automatically in the user-serving CDN caching machines. Since the hosting vendor and the CDN vendor are all the same, it is also easy to use their services. There is no incompatibility issues, interoperability issues, and better integrated analytics, are all the benefits of CDN Hosting services.

TOFFEE Benchmarks :: TOFFEE-1.1.28 ↗
Saturday' 13-Mar-2021
Here is the TOFFEE WAN Optimization benchmarks of the TOFFEE version: TOFFEE-1.1.28. This is the current TOFFEE development version till date (2-Jul-2016). This is a HPC TOFFEE variant meant for high-end custom build servers and high-end desktops (i.e High Performance Computing a.k.a HPC). TOFFEE built this way often needs customized kernel compilation and build such as processor specific and hardware specific tune-ups since it is highly CPU intensive (if not offloaded via Hardware Accelerator Cards).

Youtubeで見る - [465//1] 158 VLOG - TOFFEE WAN Optimization Software Development live update - 6-Nov-2016 ↗

TOFFEE (and TOFFEE-DataCenter) optimized Wireless Mesh-Networks - B.A.T.M.A.N [ (Open Mesh)] ↗
Saturday' 13-Mar-2021
TOFFEE/TOFFEE-DataCenter can be used to optimize Ad-Hoc Mobile Wireless Mesh-Networks. To learn more about the same here are some references: B.A.T.M.A.N. - Mobile ad hoc network (MANET) - Wireless ad hoc network (WANET) - (Open Mesh) Wiki -

Research :: Optimization of network data (WAN Optimization) at various levels:
Network File level network data WAN Optimization

Learn Linux Systems Software and Kernel Programming:
Linux, Kernel, Networking and Systems-Software online classes

Hardware Compression and Decompression Accelerator Cards:
TOFFEE Architecture with Compression and Decompression Accelerator Card [CDN]

TOFFEE-DataCenter on a Dell Server - Intel Xeon E5645 CPU:
TOFFEE-DataCenter screenshots on a Dual CPU - Intel(R) Xeon(R) CPU E5645 @ 2.40GHz - Dell Server