100mb/s speed limit, please help


  • Moderator

    @george1421 said:

    @Quazz said:

    There is a new setting called bitrate for storage nodes in trunk version of FOG that may be missing a zero (I do not mean replication bandwidth)

    First the simple answer. The bitrate is only for moving files/images between the master node and a storage node. Not between the fog server and the target computers.

    Wait, then what exactly is the difference between the replication bandwidth setting (which controls at what speeds images are allowed to replicate to other storage nodes) and the bitrate setting?


  • Moderator

    @stowtwe Thank you for the details. I see that you are using the 1.2.0 stable version and not a trunk (pre1.3.0) version. Is that correct?

    We may need to get one of the devs to verify, but image deployment (partclone) should use nfs to move files to the target computers. Your testing with iperf and ftp show that the computer is capable of transferring at wire speeds (I would expect 50MB-80MB would be your cap because of internal computer restrictions. The 125MB/s is a theoretical max for GbE network).

    So I wonder if there are inefficiencies for NFS on your version of debian. (sorry rhel person here) Isn’t wheezy a bit old?


  • Moderator

    @Quazz said:

    There is a new setting called bitrate for storage nodes in trunk version of FOG that may be missing a zero (I do not mean replication bandwidth)

    First the simple answer. The bitrate is only for moving files/images between the master node and a storage node. Not between the fog server and the target computers.



  • @stowtwe managed switches are capable of throttling specific traffic types.

    One time, I was having speed issues in an OSX environment and I finally got down to the root of the problem, the building’s managed switches were throttling AFP to 10Mbps… yeah… Check your switch.

    @Quazz good idea.


  • Moderator

    There is a new setting called bitrate for storage nodes in trunk version of FOG that may be missing a zero (I do not mean replication bandwidth)



  • Hi,
    Sorry for the lack of information. I will lay things out a bit better here for you.

    1. We are using fog 1.2.0
    2. The OS is Debian 7.9 Wheezy
    3. We are stuck at 100 Megabits for imaging. Imaging is capped at around 680 MegaBytes per Minute both ways, which equates to about 90Mbps. Adding more clients to image cuts this number between them.
    4. The FOG server is a physical desktop machine.
    5. The FOG server is connected with a CAT 5e cable to a gigabit switch.

    I tried the IPerf test before, and confirmed that I am capable of getting gigabit (1000Mbps) speeds accross the network that I am using. I have also connected to the share the images are hosted and copied them to another computer. I was able to do this at 75-100MBps, which would be most definitely be in the gigabit speed range.

    The next test I tried was FTP. I was able to FTP an image at around 50-80MBps. It is a little bit slower, but still is completely reasonable, and much faster than imaging speeds.

    All of the clients I am trying to image are connected to a gigabit switch with a Cat5e cable. The server is on the same gigabit switch.



  • I’d say do an iPerf test between the FOG server an a desktop connected to the same switch. See what happens.

    Heres instructions on that: https://iperf.fr/

    Let us know the results of the TCP speed test from client to server?


  • Moderator

    Lets start with the basics

    1. What version of fog are you using? (1.2.0 stable or an trunk version (pre1.3.0)
    2. What OS is the FOG server running?
    3. Lets just make sure we know the unit of measure. You are telling me Mb/s [mega bits] and not MB/s [mega bytes] right? (the reason why I ask is 1000Mb/s is 125MB/s so if you are seeing 100MB/s then is reasonable)
    4. Is your FOG server a physical box or is it virtual?
    5. Have you confirmed that the FOG server is connected via a GbE link? (I would assume so because each host is seeing 100mb/s according to your post)
    6. If you are able to get multiple hosts to image at 100mb/s at the same time, then you don’t have a 100mb/s switch somewhere in the database.

    To my knowledge there is no throttling for image creation, only for image replication to other storage nodes


Log in to reply
 

525
Online

5.8k
Users

13.1k
Topics

123.1k
Posts