Announcement

Collapse
No announcement yet.

Simple Patch Lets Amazon's EC2 Linux Network Driver Start ~90x Faster

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Simple Patch Lets Amazon's EC2 Linux Network Driver Start ~90x Faster

    Phoronix: Simple Patch Lets Amazon's EC2 Linux Network Driver Start ~90x Faster

    With how ubiquitous the Amazon Elastic Compute Cloud (EC2) is, one may have assumed that for years the software stack was already extensively optimized to insane levels, especially as it concerns the boot time for being able to quickly respond to changes in load... But it turns out there still is some low hanging fruit such as with Amazon's "ENA" network driver and a new patch allowing it to initialize 90 times quicker...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    the ENA driver initialization time dropped from 173 milliseconds to a mere 1.9 milliseconds
    The driver takes 1900000 nanoseconds to initialize, What waste of time!
    Last edited by Setif; 01 March 2020, 01:16 PM.

    Comment


    • #3
      ha, tell me more about big o notation and algorithmic complexity if I optimize simply by changing a timeout constant!

      Comment


      • #4
        Originally posted by Setif View Post
        The driver takes 1900 nanoseconds to initialize, What waste of time!
        it's actually 1,900,000 nanoseconds or 1900 microseconds.

        Comment


        • #5
          Haha, winner of the best clickbaitized title of the year

          Comment


          • #6
            Kinda wonder why it takes any time at all to initialize a virtual network driver. Surely the host could just leave some state somewhere to tell it where the ring buffers are, then be done with it. I guess I'll have to look at it to find out what they thought was worth doing that wasn't that.

            Comment


            • #7
              Am I the only one wondering how tightening up a 5mS polling loop shaved 170mS off the startup time ?

              If the poll itself was taking a long time then it still wouldn't take the new startup time down to 2mS.
              Test signature

              Comment


              • #8
                Biggest waste of 171.1 ms in my life. The trips I could have taken with that extra time, the mountains I could have climbed ...

                Comment


                • #9
                  While reducing the ethernet driver initialization time is overall goodness, quite honestly most of my EC2 instances take *so* much more time to startup the various applications and services that saving a hundred milliseconds is just noise....

                  Comment


                  • #10
                    While its only 171ms, cumulatively it does add up over time if they continue to resolve issues like this. That's the problem with small hanging fruit problems, often very hard to see the value until you knock a fair few of them off the tree!

                    Comment

                    Working...
                    X