2013 3rd IEEE International Advance Computing Conference (IACC) 2013
DOI: 10.1109/iadcc.2013.6514240
|View full text |Cite
|
Sign up to set email alerts
|

Performance evaluation of TCP variants under different node speeds using OPNET simulator

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
4
0

Year Published

2014
2014
2015
2015

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 4 publications
0
4
0
Order By: Relevance
“…For loads (50% and 75%) it varies from 93 msec to 122 msec and for fully utilized link (100%) load was 9.7 Sec and then for over utilized link (120%) load reaches 33.2 Sec. Figure 7 shows FTP download response time [8] which is defined as the time elapsed between sending a request and receiving the response packet.For loads (50% and 75%) it varies from 109 msec to 126 msec and for fully utilized link (100%) load was 47 Sec and then for over utilized link (120%) load reaches 208 Sec. Figure 7 shows FTP download response time [8] which is defined as the time elapsed between sending a request and receiving the response packet.For loads (50% and 75%) it varies from 109 msec to 126 msec and for fully utilized link (100%) load was 47 Sec and then for over utilized link (120%) load reaches 208 Sec.…”
Section: Fig 5: Http Page Response Timementioning
confidence: 99%
See 2 more Smart Citations
“…For loads (50% and 75%) it varies from 93 msec to 122 msec and for fully utilized link (100%) load was 9.7 Sec and then for over utilized link (120%) load reaches 33.2 Sec. Figure 7 shows FTP download response time [8] which is defined as the time elapsed between sending a request and receiving the response packet.For loads (50% and 75%) it varies from 109 msec to 126 msec and for fully utilized link (100%) load was 47 Sec and then for over utilized link (120%) load reaches 208 Sec. Figure 7 shows FTP download response time [8] which is defined as the time elapsed between sending a request and receiving the response packet.For loads (50% and 75%) it varies from 109 msec to 126 msec and for fully utilized link (100%) load was 47 Sec and then for over utilized link (120%) load reaches 208 Sec.…”
Section: Fig 5: Http Page Response Timementioning
confidence: 99%
“…Figure 7 shows FTP download response time [8] which is defined as the time elapsed between sending a request and receiving the response packet.For loads (50% and 75%) it varies from 109 msec to 126 msec and for fully utilized link (100%) load was 47 Sec and then for over utilized link (120%) load reaches 208 Sec. Figure 7 shows FTP download response time [8] which is defined as the time elapsed between sending a request and receiving the response packet.For loads (50% and 75%) it varies from 109 msec to 126 msec and for fully utilized link (100%) load was 47 Sec and then for over utilized link (120%) load reaches 208 Sec. Figure 8 shows FTP upload response time [8] which is defined as the time elapsed between sending a file and receiving the response.…”
Section: Fig 5: Http Page Response Timementioning
confidence: 99%
See 1 more Smart Citation
“…Research in [4] integrated a discussion on protocols of dynamic source routing (DSR), ad-hoc on-demand distance vector (AODV), TORA and OLSR, regarding scalability and mobility, where OLSR was the most favorite proactive routing protocol, while AODV has been designated as the most effective on-demand protocol for MANET scenarios. The author in [5] also evaluate the performance of different TCP variants such as Tahoe, Reno, New reno and SACK under different node speeds and its effect on Throughput, End to end delay, FTP download response time and FTP upload response time. Also MANET TCP optimization has been investigated in many studies [6,7].…”
Section: Introductionmentioning
confidence: 99%