The TOFFEE Project
HOMEDOCUMENTATIONUPDATESVIDEOSRESEARCHDOWNLOADSPONSORSCONTACT


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.

kiran@HP-ENVY-15:~/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
kiran@HP-ENVY-15:~/temp$

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

kiran@HP-ENVY-15:~/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
kiran@HP-ENVY-15:~/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).

kiran@HP-ENVY-15:~/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
kiran@HP-ENVY-15:~/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


Recommended Topics:

Building my own CDN - Moving away from Joomla to non-Joomla website - Update: 01-Oct-2016 ↗
Saturday' 13-Mar-2021
Seems there are couple of Inmotionhosting servers are down. And one of the server includes The TOFFEE Project website hosted server. I was in touch with the Inmotionhosting team trying to resolve the same. I found a unique issue that all my website files are intact and the Joomla database. But the Joomla database tables are completely wiped out and missing. Besides there is also a sort of upgrade going on in their servers. Luckily I have the most recent backup of the entire website.

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.

TOFFEE-DataCenter screenshots on a Dual CPU - Intel(R) Xeon(R) CPU E5645 @ 2.40GHz - Dell Server ↗
Saturday' 13-Mar-2021

My Lab HDD and SSD logs for research ↗
Saturday' 13-Mar-2021

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

TOFFEE-DataCenter WAN Optimization :: TOFFEE-DATACENTER-1.3.25-1-portable ↗
Saturday' 13-Mar-2021
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

Watch on Youtube - [466//1] 158 VLOG - TOFFEE WAN Optimization Software Development live update - 6-Nov-2016 ↗


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

TOFFEE-DataCenter WAN Optimization - Google Hangouts Demo and VOIP Optimization ↗
Saturday' 13-Mar-2021

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.

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



Featured Educational Video:
Watch on Youtube - [89//1] B.E and M.E Final Year Projects - Form your Team ↗

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

Building my own CDN - Google PageSpeed Insights - Update: 22-Jul-2016 ↗
Saturday' 13-Mar-2021
Ever since after I launched my new The TOFFEE Project website on 1-May'2016, I can see there is a steep increase in traffic. Soon after the launch when I monitored its Alexa rankings it was reporting about 12 Million or so. But once it is getting more and more traffic the Alexa rankings shot up and now currently it shows around 2 Million (as on 22-July-2016). Alexa is an excellent tool to monitor your overall website global ranking and indirectly its performance. Unlike Google Analytics which is bound one or other way into Google's SEO. Alexa gives you a second opinion about your website's growth.

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

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 DataCenter WAN Optimization - Google Hangouts demo and VOIP Optimization ↗
Saturday' 13-Mar-2021
TOFFEE DataCenter WAN Optimization - Google Hangouts demo and VOIP Optimization



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