O projeto TOFFEE
CASADOCUMENTAÇÃOATUALIZAÇÕESVÍDEOSPESQUISADESCARREGARPATROCINADORESCONTATO


DOCUMENTATION 》 TEST CASES :: TEST RESULTS :: TOFFEE-Mocha-1.0.32 asymmetric constant packet delay feature

Here are the TOFFEE-Mocha test cases and test results of new asymmetric constant packet delay feature supported in the new TOFFEE-Mocha-1.0.32 release. Click HERE to download TOFFEE-Mocha-1.0.32-1-x86_64.tar.xz and TOFFEE-Mocha-1.0.32-1-i386.tar.xz.

Here is my test network topology:
TOFFEE-Mocha asymmetric packet delay test setup

Test case1 :: no packet delay: This is a reference test with no packet delay.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case1 - no packet delay

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.34 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.34 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.36 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1.43 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.343/1.372/1.432/0.057 ms
kiran@WD-250GB:~$

Test case2 :: 1ms per packet delay: This will enable 1ms constant packet delay for all packets (i.e upstream and downstream).
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case2 - 1ms per packet delay

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=3.38 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=3.28 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=3.49 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=3.34 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 3.288/3.377/3.493/0.094 ms
kiran@WD-250GB:~$

Test case3 :: 1ms upload alone packet delay: This will enable 1ms constant packet delay for all upstream packets alone.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case3 - 1ms upload alone packet delay

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.49 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.51 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.32 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.30 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.300/2.408/2.515/0.108 ms
kiran@WD-250GB:~$

Test case4 :: 1ms download alone packet delay: This will enable 1ms constant packet delay for all downstream packets alone.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case4 - 1ms download alone packet delay

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.31 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.33 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.41 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.41 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.313/2.367/2.416/0.067 ms
kiran@WD-250GB:~$

Test case5 :: 1ms download packet delay + 1ms per packet delay: This will enable 1ms constant packet delay for all downstream packets along with constant 1ms per-packet delay.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case5 - 1ms download packet delay + 1ms per packet delay

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.36 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=4.34 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=4.43 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=4.46 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 4.342/4.401/4.465/0.049 ms
kiran@WD-250GB:~$

Test case6 :: 1ms upload packet delay + 1ms per packet delay: This will enable 1ms constant packet delay for all upstream packets along with constant 1ms per-packet delay.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case6 - 1ms upload packet delay + 1ms per packet delay

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.26 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=4.46 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=4.35 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=4.47 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 4.260/4.389/4.472/0.087 ms
kiran@WD-250GB:~$

Test case7 :: 1ms upload packet delay + 1ms download packet delay + 1ms per packet delay: This will enable 1ms constant packet delay for all upstream and downstream packets along with constant 1ms per-packet delay.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case7 - 1ms upload packet delay + 1ms download packet delay + 1ms per packet delay

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=5.26 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=5.41 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=5.66 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=5.31 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=5.37 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=5.29 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=5.41 ms
^C
--- 192.168.0.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 5.260/5.391/5.662/0.130 ms
kiran@WD-250GB:~$



Tópicos sugeridos:


TOFFEE-Mocha - WAN Emulator


Categories

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


Tópicos recomendados:

TOFFEE hardware selection guide ↗
Saturday' 13-Mar-2021
When you build a WAN Optimization device with TOFFEE the entire packet processing (data optimization) takes place in software layer or in other words more precisely Operating System kernel space. However if you have any compression or encryption hardware accelerator hardware card the parts of the TOFFEE packet processing modules can be offloaded to hardware layer and thus improving its efficiency.

Introducing TrueBench - a high resolution CPU benchmarking system ↗
Saturday' 13-Mar-2021
TrueBench is an unique open-source benchmarking system in which the core system performance and efficiency parameters are measured at extreme high resolution in the order of several million/billion µ-seconds for a given specific task. TrueBench is a part of The TOFFEE Project research. With TrueBench Raspberry Pi 3, Raspberry Pi 2B, Raspberry Pi 2 and other embedded SoC devices are benchmarked and you can do a comparative analysis with standard mainstream x86 devices.

TOFFEE-Mocha WAN Emulation software development - Update: 16-June-2016 ↗
Saturday' 13-Mar-2021
I started TOFFEE-Mocha WAN Emulation software development on 1-June-2016. I took the existing TOFFEE components as a base. Although the TOFFEE-Mocha is entirely an independent fresh Open-Source WAN Emulation solution. Ever since I am in the process of defining and inventing features. So far I come up with the most important feature which is expected to be present in any WAN Emulation software is the packet delay option.

TOFFEE-Butterscotch Bandwidth saver software development - Update: 28-Oct-2016 ↗
Saturday' 13-Mar-2021
Here is my first software development update of TOFFEE-Butterscotch. In my first TOFFEE-Butterscotch news update I have introduced about TOFFEE-Butterscotch research, project specifications, use-cases, etc. Introducing TOFFEE-Butterscotch Alerts: These are simple packet counters which corresponds to the filter type. For example if the incoming TCP-SYN packets are blocked then its corresponding alert counter will increment whenever such a packet arrives and gets filtered (dropped).

TOFFEE deployment topology guide ↗
Saturday' 13-Mar-2021
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).

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.



Building my own CDN - Minify Script files - Update: 23-July-2016 ↗
Saturday' 13-Mar-2021
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.

Introducing TOFFEE-Butterscotch - Save and Optimize your Internet/WAN bandwidth ↗
Saturday' 13-Mar-2021
TOFFEE-Butterscotch yet another variant of TOFFEE can be used to save and optimize your Home/SOHO Internet/WAN bandwidth. Unlike TOFFEE (and TOFFEE-DataCenter) TOFFEE-Butterscotch is a non peer-to-peer (and asymmetric) network optimization solution. This makes TOFFEE-Butterscotch an ideal tool for all Home and SOHO users.

WAN Optimization - Animated demo of Packet Optimization in TOFFEE-DataCenter ↗
Saturday' 13-Mar-2021

Demo TOFFEE-DataCenter WAN Optimization VM Test Setup ↗
Saturday' 13-Mar-2021



Featured Educational Video:
Assista no Youtube - [17445//1] 294 - VRF - Virtual Routing and Forwarding - Introduction ↗

TOFFEE-Butterscotch Documentation :: TOFFEE-Butterscotch-1.0.11-rpi2-23-nov-2016 ↗
Saturday' 13-Mar-2021
TOFFEE-Butterscotch Documentation :: TOFFEE-Butterscotch-1.0.11-rpi2-23-nov-2016

TOFFEE (and TOFFEE-DataCenter) deployment with VPN devices ↗
Saturday' 13-Mar-2021
In case if you need to deploy TOFFEE along with your existing VPN devices you can deploy the same as shown below. This will allow your VPN devices to encrypt your TOFFEE WAN Optimized network data. NOTE: Make sure about the VPN deployment topology done in the right order. Else TOFFEE (LAN side) may get VPN encrypted packets which may not be possible (and or difficult) to further optimize. Hence always make sure to deploy them in a topology suggested below so that TOFFEE devices are out of VPN tunnel.

CDN Content Delivery Networks - Types ↗
Saturday' 13-Mar-2021

Building my own CDN - Minify Script files - Update: 23-July-2016 ↗
Saturday' 13-Mar-2021
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.




Building my own CDN - Finally Completed - Update: 17-Dec-2017 ↗
Saturday' 13-Mar-2021
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.



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 [CDN]


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