LAN and WAN tests (II)
LAN test result:
Sources were deployed on gridfarm machines and client was deployed on complexity machine. The average transfer speed is around 70 Mbps. For the same situation -4 parallel streams- PTCP transfer speed is around 80 Mbps. Total file size is around 185MB and the bandwidth usage of each source:
WAN test result:
Like LAN tests, sources were deployed on gridfarm machines and client was deployed on pipeline3 machine, San Diego. The same performance pattern in LAN has been observed, too. The average transfer speed for Gridtorrent around is 17 Mbps and for PTCP -4 parallel streams- is around 27 Mbps.
Observations:
In both LAN and WAN there is an about 10 Mbps drop observed on Gridtorrent transfer. I think this drop is normal due to nature of Gridtorrent. In PTCP, when the communication is set, there is not communication overhead any more. Just data is transfered. However, in Gridtorrent, there is a request overhead for each piece and blocks of each pieces, and integrity of each piece is verified by hash-code checking. This communication and hash-code checking overhead degrades overall data transfer. Even though, the drop in data transfer speed, sources bandwidth usage seems balanced which is the main point of Bittorrent inspired Gridtorrent.
Many Gridtorrent parameters were changed to see how its performance behaves under those changes. But there is no significant effect on performance gain of Gridtorrent.
11/08/2006, Bloomington
Sources were deployed on gridfarm machines and client was deployed on complexity machine. The average transfer speed is around 70 Mbps. For the same situation -4 parallel streams- PTCP transfer speed is around 80 Mbps. Total file size is around 185MB and the bandwidth usage of each source:
| source1 | source2 | source3 | source4 |
| 44MB | 53MB | 47MB | 41MB |
WAN test result:
Like LAN tests, sources were deployed on gridfarm machines and client was deployed on pipeline3 machine, San Diego. The same performance pattern in LAN has been observed, too. The average transfer speed for Gridtorrent around is 17 Mbps and for PTCP -4 parallel streams- is around 27 Mbps.
| source1 | source2 | source3 | source4 |
| 52MB | 45MB | 42MB | 46MB |
Observations:
In both LAN and WAN there is an about 10 Mbps drop observed on Gridtorrent transfer. I think this drop is normal due to nature of Gridtorrent. In PTCP, when the communication is set, there is not communication overhead any more. Just data is transfered. However, in Gridtorrent, there is a request overhead for each piece and blocks of each pieces, and integrity of each piece is verified by hash-code checking. This communication and hash-code checking overhead degrades overall data transfer. Even though, the drop in data transfer speed, sources bandwidth usage seems balanced which is the main point of Bittorrent inspired Gridtorrent.
Many Gridtorrent parameters were changed to see how its performance behaves under those changes. But there is no significant effect on performance gain of Gridtorrent.
11/08/2006, Bloomington
posted by Ali Kaplan at Wednesday, November 08, 2006
2 Comments:
What is parallel TCP scenario; does it run from just one source?
On LAN what is TCP performance. PTCP should not gain much on LAN over TCP
Data has been transferred from a single source to single client with 4 parallel TCP streams on both LAN and WAN. Parallel TCP does not have substantial performance gain on LAN unlike on WAN, but it has better performance than TCP
on LAN.
The question here is that Gridtorrent's performance which is not better than PTCP on LAN and WAN can be acceptable as fast large volume scientific data transfer?
Post a Comment
<< Home