#8454: Very low network performance with a Marvell Yukon card. ---------------------------------------------+---------------------------- Reporter: bga | Owner: nobody Type: bug | Status: new Priority: high | Milestone: R1 Component: Drivers/Network/marvell_yukon | Version: R1/Development Resolution: | Keywords: Blocked By: 8743 | Blocking: Has a Patch: 1 | Platform: All ---------------------------------------------+---------------------------- Comment (by jstressman): One other thing for me that seemed to really improve responsiveness and performance was to disable my 2 interfaces that I wasn't using. I disabled atheros0 and marvell_yukon0 and only use marvell_yukon1. I'd have to do more testing to see if I could give a more solid explanation of this and confirm that it is indeed the case... but Web+ at least seemed to respond considerably quicker and more smoothly once I'd disabled the unused interfaces. I'm still using the old driver at the moment, so I'd want to retest this to figure out whether it was the new driver or the old driver that I saw this behavior under... and if it's really related to the driver at all, or some kind of bad routing, or just Web+ trying an invalid interface before timing out and trying a good one... or even something like trying an invalid ipv6 route before falling back to a working ipv4... I really have no idea at the moment, but wanted to point out what I thought I saw in case it gives anyone an idea. One other idea I had was that it was related to the atheros driver spitting out 1kB a second in verbose logs to the syslog, and disabling that interface shut it up and increased performance on my remaining interface(s)? -- Ticket URL: <http://dev.haiku-os.org/ticket/8454#comment:28> Haiku <http://dev.haiku-os.org> Haiku - the operating system.