praecorloth
Contributor
- Joined
- Jun 2, 2011
- Messages
- 159
So I've got a FreeNAS 8.0.3 box and performance has been so/so. It's been worse, when I first started this I didn't realize my NIC was 100Mbit. :) But since switching to gigabit, I've lived with vastly-superior-to-100Mbit-but-still-not-gigabit performance. I'm topping off just shy of 400Mbit on the reports. So given all of the fun testing I've done in the past, I went to iperf. I fired up the server side on a FreeNAS with a 16K frame, then I ran a client from my Windows box, and a Linux box. Both came back around the 650-700Mbit range. Not good, but not terrible. Linux as the server and Windows as the client came back at 950+Mbit. FreeNAS as the client came back at about 400-450Mbit. Hrm.
So FreeNAS has trouble both as the server and as a client, but definitely more so as a client. What could this mean? I did a netstat -i on the FreeNAS box and it didn't show any collisions. I'm fairly certain, though I can test when I get home, that there have been a couple of different cables between the FreeNAS box and the switch. I might even be able to try a different NIC. But...
It'll still be a Realtek NIC. I had heard a while back that there was a pretty terribad Realtek driver floating around the *nix world recently. Does anyone know how I would go about checking what driver I'm using? I could then go back and see if it's the same driver that people have been complaining about.
So FreeNAS has trouble both as the server and as a client, but definitely more so as a client. What could this mean? I did a netstat -i on the FreeNAS box and it didn't show any collisions. I'm fairly certain, though I can test when I get home, that there have been a couple of different cables between the FreeNAS box and the switch. I might even be able to try a different NIC. But...
It'll still be a Realtek NIC. I had heard a while back that there was a pretty terribad Realtek driver floating around the *nix world recently. Does anyone know how I would go about checking what driver I'm using? I could then go back and see if it's the same driver that people have been complaining about.