Документация :: Документация :: TOFFEE-Mocha - WAN Emulator

My 500GB Seagate Barracuda 7200RPM hard-drive suddenly started making mild clicking noise. I found this happening since morning. I was suspicious that something wrong in this drive and when I opened the Linux Disks app, I can find the cause of this issue. The disk is increasingly getting read errors. Besides I can see various other parameters such as Power-On Hours, Temperature, Head flying hours, etc.

Download TOFFEE-DATACENTER-1.3.25-1-portable.tar.xz via Google Drive share: platform independent (portable) source: TOFFEE-DATACENTER-1.2.2-1-portable.tar.xz * Alternatively download from SOURCEFORGE project site. * Here are the TOFFEE-DataCenter supported features. * To know more about the project kindly refer TOFFEE-Datacenter Documentation, News and Updates

Today I finally completed building my own private CDN. As I discussed so far in my earlier topics (Building my own CDN), I want to custom build the same step-by-step from scratch. And I don't want to for now use/buy third-party CDN subscriptions from Akamai, CloudFlare, Limelight, etc as I discussed earlier.

If you want to deploy TOFFEE along with a web-proxy cache (such as Squid Proxy) you can deploy the same as shown below. TOFFEE does not cache files. TOFFEE does packet level network optimization. So if you want caching your web content you can use transparent mode web-proxy cache intercepting your WAN links. A web-proxy may reduce amount of data being processed (optimized) within these TOFFEE devices and so reduce the CPU overheads and improve its performance.

Here is a quick demo of TOFFEE WAN Optimization optimizing MySQL Data transfers of a MySQL Client to Server Remote Access.

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 cdn1.the-toffee-project.org, cdn2.the-toffee-project.org 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.

Download TOFFEE-MOCHA-2.0.3-0-10-nov-2018-x86-64.iso via Google Drive share: Live bootable x86-64 Debian Stretch 9.5 with light-weight LXDE UI ISO (includes source-code): TOFFEE-MOCHA-2.0.3-0-10-nov-2018-x86-64.iso You can find the source tar-ball in the /root folder. To know more about the project kindly refer TOFFEE- Mocha: News and Updates - Documentation. To know more about current specific release, objectives, features, release notes/updates, quick demo and future road-map, you can watch my video below.

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.

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.

One of the suggestions Google PageSpeed Insights tool suggested for The TOFFEE Project website is to minify the css and java script files. Minify Script files: When you read online about minification of your web script files, often they highlight file size savings and thus resulting faster download time and better website performance.

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 cdn1.the-toffee-project.org, cdn2.the-toffee-project.org 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.