TOFFEEプロジェクト
ホームドキュメンテーション更新ビデオ研究ダウンロードスポンサー接触


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:~$



Suggested Topics:


TOFFEE-Mocha - WAN Emulator


Categories

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


おすすめトピック:

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 emulator Lab deployment and topology guide ↗
Saturday' 13-Mar-2021

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

TOFFEE-Mocha WAN Emulator Jitter Feature ↗
Saturday' 13-Mar-2021

Setting up a WAN Emulator within VirtualBox ↗
Saturday' 13-Mar-2021

Moon Base and Space Colonization - First we need fast InterPlanetary Internet ↗
Saturday' 13-Mar-2021

Youtubeで見る - [1888//1] Deep Space Communication - Episode1 - Introduction ↗


TOFFEE (and TOFFEE-DataCenter) deployment in SD-WAN Applications ↗
Saturday' 13-Mar-2021
Software-Defined Wide Area Networking (SD-WAN) is a new innovative way to provide optimal application performance by redefining branch office networking. Unlike traditional expensive private WAN connection technologies such as MPLS, etc., SD-WAN delivers increased network performance and cost reduction. SD-WAN solution decouple network software services from the underlying hardware via software abstraction.

Optimization of network data (WAN Optimization) at various levels ↗
Saturday' 13-Mar-2021
WAN Network data can be optimized at various levels depending upon the network applications, protocols, topology and use-cases. So the amount of data you can optimize will depend on the strategy you choose to optimize. Such as: Network Packet level optimization, Session level optimization, File level optimization, etc.

Building my own CDN - choosing a web-hosting to deploy my CDN - Update: 28-July-2016 ↗
Saturday' 13-Mar-2021
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.

TOFFEE-DataCenter WAN Optimization software development - Update: 13-Aug-2016 ↗
Saturday' 13-Mar-2021
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.



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

Moon Base and Space Colonization - First we need fast InterPlanetary Internet ↗
Saturday' 13-Mar-2021

A study on WAN Optimization Techniques ↗
Saturday' 13-Mar-2021
There are various techniques with which one can optimize their WAN Network Data. Any long distance communication can be considered as WAN Network. A decade ago any network connecting two countries, considered as a WAN network, and a network within a city as MAN and soon. But these days in general any long distance communication is considered as WAN Network. Such as your Mobile communication networks, Satellite networks, Space Networks (Deep space networks), Trans-Atlantic cable networks, etc.

Multi-dimensional (Multi-universe) Internet Technology - A Proposal ↗
Saturday' 13-Mar-2021
Currently what we have is a single homogeneous (sort of) WWW Internet. Which we can consider as a single-dimensional network. What I propose is that we can create complete independent multiple Internets with each Internet having its own IP-address space, Domain namespace and an authority to manage Domain names. And these networks/Internets can be entirely IPv4 only based or IPv6 only based.

Demo TOFFEE-DataCenter WAN Optimization packaging feature ↗
Saturday' 13-Mar-2021




TOFFEE-Butterscotch Bandwidth saver software development - Update: 17-Nov-2016 ↗
Saturday' 13-Mar-2021
Here is my second software development update of TOFFEE-Butterscotch. In the previous update (28-Oct-2016) I discussed about the Alerts, etc. Whereas in my first TOFFEE-Butterscotch news update I have introduced about TOFFEE-Butterscotch research, project specifications, use-cases, etc.



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