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


DOCUMENTATION 》 TEST CASES :: TEST RESULTS :: TOFFEE-Mocha-1.0.14 Development version

Here are the TOFFEE-Mocha test cases and test results of the upcoming new TOFFEE-Mocha which is still under development. The features of this TOFFEE-Mocha are discussed in the software development update: TOFFEE-Mocha WAN Emulation software development - Update: 1-July-2016

Test case1 :: 999 millisecond constant packet delay: As you can see unlike 40 milliseconds the maximum limit which existed earlier, the new 999 milliseconds delay range allows users to slow down the transfer rates even further.

[email protected]:~/temp$ ping 192.168.0.1 -s 1000
PING 192.168.0.1 (192.168.0.1) 1000(1028) bytes of data.
1008 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2000 ms
1008 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2000 ms
1008 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2000 ms
1008 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2000 ms
1008 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=2998 ms
1008 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=2997 ms
1008 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3995 ms
1008 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=3985 ms
1008 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=3984 ms
1008 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=3984 ms
1008 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=3983 ms
1008 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=3982 ms
1008 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=3984 ms
1008 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=3982 ms
^C
--- 192.168.0.1 ping statistics ---
18 packets transmitted, 14 received, 22% packet loss, time 17007ms
rtt min/avg/max/mdev = 2000.042/3277.214/3995.537/873.965 ms, pipe 4
[email protected]:~/temp$

Test case2 :: 500 millisecond constant packet delay: With 500 milliseconds you get roughly double the performance of 999 milliseconds.

[email protected]:~/temp$ ping 192.168.0.1 -s 1000
PING 192.168.0.1 (192.168.0.1) 1000(1028) bytes of data.
1008 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=1488 ms
1008 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1481 ms
1008 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=1481 ms
1008 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1008 ms
1008 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=1002 ms
^C
--- 192.168.0.1 ping statistics ---
11 packets transmitted, 10 received, 9% packet loss, time 10017ms
rtt min/avg/max/mdev = 1002.077/1147.151/1488.063/220.133 ms, pipe 2
[email protected]:~/temp$

Test case3 :: 500 millisecond constant packet delay + random packet delay: With constant delay (in this case 500 milliseconds) if you enable the new random packet delay feature, it will skip delay randomly few packets. Which can be controlled via random delay factor. In this case the random delay factor value is set to 1. And you can see below few packets are not delayed. Hence their ping response time almost reduced to half (i.e around 500 ms).

[email protected]:~/temp$ ping 192.168.0.1 -s 1000
PING 192.168.0.1 (192.168.0.1) 1000(1028) bytes of data.
1008 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1503 ms
1008 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1497 ms
1008 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=1001 ms
1008 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=1001 ms
1008 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=419 ms
1008 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1001 ms
1008 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=1001 ms
1008 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=502 ms
1008 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=502 ms
1008 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=1002 ms
1008 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=1001 ms
1008 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=1002 ms
^C
--- 192.168.0.1 ping statistics ---
22 packets transmitted, 21 received, 4% packet loss, time 21029ms
rtt min/avg/max/mdev = 419.093/974.135/1503.026/250.662 ms, pipe 2
[email protected]:~/temp$

Random Packet delay: As discussed in my VLOG/update earlier, the idea of Random packet delay is to introduce the fluctuating, bursty nature of packet flow. So here are various tests done which shows the same in action. These tests below are performed while downloading a large file by enabling random packet delay along with various values of constant packet delay.

Test case4 :: 2 millisecond constant packet delay + random packet delay: With constant delay of 2 millisecond and random packet delay you can notice the blue curve which almost appears constant. The traffic in this case is bursty but it is not that significant to notice in the graph shown below.
TOFFEE_Mocha_2ms_delay_with_random_packet_delay

Test case5 :: 10 millisecond constant packet delay + random packet delay: With constant delay of 10 millisecond and random packet delay you can notice the blue curve which almost appears constant. The traffic in this case is bursty but it is not that significant to notice in the graph shown below. But it appears somewhat fluctuating than the 5 millisecond test case4 above.
TOFFEE_Mocha_10ms_delay_with_random_packet_delay

Test case6 :: 200 millisecond constant packet delay + random packet delay: With constant delay of 200 millisecond and random packet delay you can notice the fluctuating blue curve. With this we can understand the true purpose of random packet delay.
TOFFEE_Mocha_200ms_delay_with_random_packet_delay

Test case7 :: 200 millisecond constant packet delay + WITHOUT random packet delay: With constant delay of 200 millisecond and WITHOUT random packet delay feature enabled you can notice the steady blue curve. This is a direct comparison of a test case with constant packet delay 200 millisecond with and without random packet delay. With random packet delay it makes the network performance choppy, fluctuating and bursty, but without random packet delay feature the network performance appears almost constant.
TOFFEE_Mocha_200ms_delay_without_random_packet_delay

So in my next upcoming TOFFEE-Mocha release I may include all these new features and updated old features. If you are in need of any specific feature (or scenario) you can kindly let know. If plausible and feasible I can support the same and release as a part of my upcoming TOFFEE-Mocha release. Kindly stay tuned !



Suggested Topics:


TOFFEE-Mocha - WAN Emulator


Categories

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


おすすめトピック:

TOFFEE-DataCenter :: Optimized ISP backbone networks for countries with slowest Internet Speed ↗
Saturday' 13-Mar-2021

IP Header Compression in WAN Links and TOFFEE-DataCenter WAN Optimization ↗
Saturday' 13-Mar-2021

TOFFEE-Mocha Documentation :: TOFFEE-Mocha-1.0.14-1-x86_64 ↗
Saturday' 13-Mar-2021

Network Latency and Bandwidth Assessment - for Network Admins and Infrastructure Architects ↗
Saturday' 13-Mar-2021

TOFFEE-DataCenter - First Live Demo and software development - Update: 26-Aug-2016 ↗
Saturday' 13-Mar-2021
Today I have done a test setup so that I can able to connect my Android Samsung Tab via TOFFEE DataCenter. Below is my complete test topology of my setup. For demo (and research/development) context I configured TOFFEE DataCenter in engineering debug mode. So I do not need two devices for this purpose.

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.



TOFFEE-Mocha - WAN Emulator :: TOFFEE-MOCHA-2.0.3-0-10-nov-2018-x86-64.iso ↗
Saturday' 13-Mar-2021
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.

Tracking Live Network Application Data - in a WAN Acceleration (WAN Optimization) Device ↗
Saturday' 13-Mar-2021

TOFFEE Download :: TOFFEE-1.1.70-1-portable ↗
Saturday' 13-Mar-2021

Why TOFFEE is forked from TrafficSqueezer ↗
Saturday' 13-Mar-2021
TrafficSqueezer is an open-source WAN Optimization project. TrafficSqueezer is mainly a research project which is started around mid-2006. It is initially started as a research (or prototype) code even before it is officially registered in Sourceforge.net. But this code is just primitive user-space raw socket modules. This is later refined and a pre-alpha version is created. Followed by which Alpha release. This prototype code is moved from user-space to Linux Kernel (Kernel Space) and then the journey begin in terms of making a serious WAN Optimization solution. Once the pre-beta and beta releases are complete the mainstream series is started.



Featured Educational Video:
Youtubeで見る - [81//1] B.E and M.E Final Year Projects - Form your Team ↗

Introducing TOFFEE-DataCenter ↗
Saturday' 13-Mar-2021
TOFFEE TOFFEE Data-Center is specifically meant for Data Center, Cluster Computing, HPC applications. TOFFEE is built in Linux Kernel core. This makes it inflexible to adapt according to the hardware configuration. It does sequential packet processing and does not scale up well in large multi-core CPU based systems (such as Intel Xeon servers, Core i7 Extreme Desktop systems,etc). Apart from this since it is kernel based, if there is an issue in kernel, it may crash entire system. This becomes a challenge for any carrier grade equipment (CGE) hardware build.

The TOFFEE Project :: TOFFEE-DataCenter :: WAN Optimization ↗
Saturday' 13-Mar-2021
The TOFFEE Project :: TOFFEE-DataCenter :: Linux Open-Source WAN Optimization

Amazon Prime video - Video Acceleration No more Buffering Problems - WAN Acceleration ↗
Saturday' 13-Mar-2021

Power consumption of my Home Lab devices for research ↗
Saturday' 13-Mar-2021
Here is my power-consumption measurements of various devices deployed within my home lab. I measured via my kill-a-watt sort of power-meter which is fairly reliable and accurate. I checked its accuracy with various standard load such as Philips LED laps and other constant power-consuming devices to make sure that the power-meter is precise.



Youtubeで見る - [976//1] 293 - iPerf Network Optimization - WAN Optimization Demo ↗

YouTube Video Network Traffic Optimization - WAN Optimization Demo ↗
Saturday' 13-Mar-2021



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


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