Hi Stefan, Interesting finding indeed, looks like the author has only tested on Xen-4.4 and the EC2 instance type that we use report Xen-3.4 as the logline below shows:
Xen version: 3.4.3.amazon (preserve-AD) I'm using a common S3 url in my test cases and the results are the same either using curl or ab to measure the download speed. I've used iperf and netperf between two of our instances and got similar results, the difference is that using the S3 url is noticeable. What is also interesting is that despite the fact that Lucid (with kernel 3.8.11) instance shows GRO as enabled it may not actually use GRO at all since the GRO API was only introduced on 3.13 and that could mean the processing impact will remain the same in both instances, I will try to measure this and will report but in the meanwhile let me know if is there anything I can mesure that may help to identify the issue. Thanks, Rodrigo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391339 Title: Trusty kernel inbound network performance regression when GRO is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1391339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
