Results 1 to 8 of 8

Thread: Major Network Performance Regressions In Linux

  1. #1
    Join Date
    Jan 2007
    Posts
    15,678

    Default Major Network Performance Regressions In Linux

    Phoronix: Major Network Performance Regressions In Linux

    Affecting the latest Linux kernel release, Linux 3.7, are "multiple apparently unrelated network performance issues." The major network performance problems were reported by a well-known Linux kernel developer...

    http://www.phoronix.com/vr.php?view=MTI2Nzc

  2. #2
    Join Date
    May 2012
    Posts
    946

    Default

    https://lkml.org/lkml/2013/1/6/34
    OK good news here, the performance drop on the myri was caused by a
    problem between the keyboard and the chair. After the reboot series,
    I forgot to reload the firmware so the driver used the less efficient
    firmware from the NIC (it performs just as if LRO is disabled).

    That makes me think that I should try 3.8-rc2 since LRO was removed
    there :-/

    The only remaining issue really is the loopback then.

    https://lkml.org/lkml/2013/1/6/54
    Just for the record, I tested 3.8-rc2, and the myri works as fast with
    GRO there as it used to work with LRO in previous kernels. The softirq
    work has increased from 26 to 48% but there is no performance drop when
    using GRO anymore. Andrew has done a good job !

  3. #3
    Join Date
    Oct 2012
    Posts
    299

    Default

    thank you for the heads up!

  4. #4
    Join Date
    Dec 2008
    Location
    Vermont
    Posts
    110

    Default

    It certainly is a performance regression, but I seriously doubt that it affects many Phoronix readers. I don't know how many of us use 10 GigE, but you have to start there, and then question how many of those readers have the Myri cards.

    Yep, it's a driver problem. For that small subset, it's pretty darned serious, but then again, it'll be fixed when 3.8 hits the streets.

  5. #5
    Join Date
    Aug 2010
    Posts
    28

    Default

    I think the problem is much more than a single driver or a simple performance regression. I updated a machine with gigabit Broadcom network to 3.7.1 . I started seeing processes hang when performing network operations--jdbc/memcached/activemq. The hangs were intermittent but would happen during heavy batch processing every night. Over the next several days, I tried messing with kernel settings, MTU settings, hugepage support settings, jdbc driver updates, jdbc driver reverts, disabling ipv6, enable/disable tcp keepalive, etc.

    I eventually reverted the setting changes back and reverted the kernel back to a 3.6 release and haven't see one hang since. I came across some lkml mailings talking about epoll hangs and figured there must be something going on, since the stack traces I was seeing were showing strange kernel hangs--like the client was waiting on the server and the server was waiting on the client

    I'll be following the progress on this network issue now to see what's uncovered.

  6. #6
    Join Date
    Dec 2011
    Posts
    128

    Default

    Quote Originally Posted by mgmartin View Post
    I think the problem is much more than a single driver or a simple performance regression. I updated a machine with gigabit Broadcom network to 3.7.1 . I started seeing processes hang when performing network operations--jdbc/memcached/activemq. The hangs were intermittent but would happen during heavy batch processing every night.
    Have you reported this to the devs?

  7. #7
    Join Date
    Aug 2010
    Posts
    28

    Default

    Initial tests using 3.7.2 look positive. I haven't seen the lockups I mentioned I had under 3.7.1 .

  8. #8
    Join Date
    Aug 2010
    Posts
    28

    Default

    I spoke too soon. Back to a 3.6 kernel.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •