Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

transfer throughput of single node #10

Open
vkuznet opened this issue Mar 24, 2017 · 12 comments
Open

transfer throughput of single node #10

vkuznet opened this issue Mar 24, 2017 · 12 comments

Comments

@vkuznet
Copy link
Owner

vkuznet commented Mar 24, 2017

We need to find out empirically a node throughput based on hardware specs, i.e. is it better to transfer 10 files at once or 100?

@rishiloyola
Copy link
Collaborator

@vkuznet Can you tell me more about this? I guess we can resolve this issue by current tests.

@vkuznet
Copy link
Owner Author

vkuznet commented Aug 13, 2017

Rishi, we need to test how much simultaneous transfers single node can sustain and how it's throughput drops with adding new transfer. To answer this question you need to create N files of equal size and start transfers each of them one at a time, i.e. start one, then another, then another. Each time you can measure how throughput drop if you new transfer is added to the pool. Eventually you need to find how much simultaneous transfer node can sustain.

@rishiloyola
Copy link
Collaborator

rishiloyola commented Aug 14, 2017

  • I performed this test. One thing I can conclude is if the two requests have shared resources then their transfer rates eventually drops and become extremely low(around 20Mb). In the beginning, I was transferring two same files(shared resource) with the rate of 20 Mb. While processing those two requests, I approved one different kind of request to transfer the data. Suddenly, the transfer rate increased and reached up to the 450 Mb.

  • With the adding a new transfer request its throughput is sometimes increasing and sometimes decreasing. I didn't see any specific changes in its throughput.

  • Without having the shared resources, it is sending the data with the rate of 400-500Mb.

@vkuznet
Copy link
Owner Author

vkuznet commented Aug 14, 2017 via email

@rishiloyola
Copy link
Collaborator

I am considering the two same files as a shared resources. Not any other quantities.

@rishiloyola
Copy link
Collaborator

rishiloyola commented Aug 14, 2017

I have Red Hat, Inc Virtio network device. Which is a para-virtualized driver. So I can calculate speed using iperf like tools. I tried to install it on uibo-cms-02.cr.cnaf.infn.it but it failed. I will do it using pre compiled binary on tomorrow.

Reference: https://serverfault.com/questions/738840/get-link-speed-of-an-virtio-net-network-adapter

@vkuznet
Copy link
Owner Author

vkuznet commented Aug 15, 2017 via email

@rishiloyola
Copy link
Collaborator

rishiloyola commented Aug 16, 2017

Here is the iperf test result between source-server and main-agent:

------------------------------------------------------------
Client connecting to main-agent.cern.ch, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[  3] local 188.185.113.130 port 38230 connected with 188.185.100.222 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  1.67 GBytes  1.44 Gbits/sec

@vkuznet
Copy link
Owner Author

vkuznet commented Aug 16, 2017

and what is throughput of network card 100Mbit/sec, 1Gbit/sec or 10Gbit/sec?

@rishiloyola
Copy link
Collaborator

I guess it's 1.44 Gbits/sec. I checked out on both the side(server and client). It is transferring all the data successfully.

@vkuznet
Copy link
Owner Author

vkuznet commented Aug 16, 2017 via email

@rishiloyola
Copy link
Collaborator

@vkuznet I searched it on the internet but could not find specific information related to throughput.
The output of lshw -class network command.

 *-network
       description: Ethernet controller
       product: Virtio network device
       vendor: Red Hat, Inc
       physical id: 3
       bus info: pci@0000:00:03.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: msix bus_master cap_list rom
       configuration: driver=virtio-pci latency=0
       resources: irq:10 ioport:c0a0(size=32) memory:febd1000-febd1fff memory:fe000000-fe003fff memory:feb80000-febbffff
     *-virtio0
          description: Ethernet interface
          physical id: 0
          bus info: virtio@0
          logical name: eth0
          serial: 02:16:3e:01:b7:d6
          capabilities: ethernet physical
          configuration: broadcast=yes driver=virtio_net driverversion=1.0.0 ip=188.185.113.130 link=yes multicast=yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants