RESEARCH 》 Network Latency in WAN Networks and performance optimization

This is my next software development update of TOFFEE-DataCenter which I am working since past few weeks. I was very busy in implementing the core TOFFEE-DataCenter components along with prototyping, benchmarking, implementing and testing the same. However today is the first time ever I did a fresh new CLI interface for the upcoming new TOFFEE-DataCenter.

Today I completed doing all the changes which are meant for the new upcoming TOFFEE-Mocha release. I have increased the resolution and the range of all factor variables. Instead 1 to 10 range now they have a range of 1 to 30. Unlike before the value 1 means it is lot more intense (or in some cases less intense) and the uppermost value 30 means lot less intense (or in some cases lot intense).

LoRaWAN - Network Optimization via TOFFEE WAN Optimization

TOFFEE-Mocha is my dream project which I thought working on it since several years. I want to make a WAN emulation software which is straight forward and simple to use. I used tc scripts along with iptables for testing my TOFFEE (and TrafficSqueezer before TOFFEE) and I am not quite satisfied with the same. As one can understand these scripts are not meant for WAN emulation.

Earlier the TOFFEE is intended to work on IoT devices, Satellite Networks, branch office/SOHO deployments. In most cases the users may deploy just one or couple of TOFFEE devices per site. But in the case of TOFFEE-DataCenter, users can scale-up deploying the same in multiple servers in a sort of distributed cluster computing scenario. Besides the core TOFFEE-DataCenter components (such as packet processing engine/framework), I need to do lot of changes in its Graphical User Interface (GUI) too to address these new requirements.

Assume you have two sites (such as Site-A and Site-B) connected via slow/critical WAN link as shown below. You can optimize this link by saving the bandwidth as well possibly improve the speed. However, the WAN speed can be optimized only if the WAN link speeds are below that of the processing latency of your TOFFEE installed hardware. Assume your WAN link is 12Mbps, and assume the maximum WAN optimization speed/capacity of Raspberry Pi is 20Mbps, then your link will get speed optimization too. And in another case, assume your WAN link is 50Mbps, then using the Raspberry Pi as WAN Optimization device will actually increase the latency (i.e slows the WAN link). But in all the cases the bandwidth savings should be the same irrespective of the WAN link speed. In other words, if you want to cut down the WAN link costs via this WAN Optimization set up, you can always get it since it reduces the overall bandwidth in almost all the cases (including encrypted and pre-compressed data).

Today I refined the first page consolidated report graphs. TOFFEE-Mocha (unlike TOFFEE) is a WAN Emulator, so the graphs are supposed to highlight this purpose and should display the overall network activity. Unlike TOFFEE, the TOFFEE-Mocha report should contain in general what is received versus what is sent across the wire. In case if the packet drop feature is enabled, you should see few missing bytes and packets. Similarly in future I may support packet duplication feature, in that case you may see more packets/bytes sent versus the packets/bytes actually received.