Duffs,
You are confused. One, we'd need to know what card it is and the driver in order to tell you what "limitations" it has.
What are the problems you have had with performance? Do you realize that even a 1Gbit card is really only running around 100 Megabytes per second, assuming your switch can even handle that?
Are you configuring the switch and card as full duplex or as auto detect? Most Gigabit and faster connections recommend auto detection for optimal performance.
Without knowing what your issue is, we cannot help you. Does the app send lots of small packets or fewer large ones? Do you do interrupt coalescence? Are you using Nagle's algorithm?
Have you tuned your kernel parameters?
The metrics you have shown have only told us how many packets have hit the wire, and no time frame, or anything.
Let me ask you. How many gallons should it take for me to get to work by driving?
I have not told you how far it is, how fast I drive, what car it is, how well tuned it is, etc, or the inflation of my tires.
---------- Post updated at 03:22 PM ---------- Previous update was at 11:37 AM ----------
Quote:
Originally Posted by
methyl
I think you need to post the difference between two samples over a given reasonable period of time.
Depending on what network kit this server is plugged into, auto-negotiation should be avoided. It usually needs turning off on the server and the LAN port. Similarly anywhere where network components are cascaded.
It looks like auto-negotiation is off on your server.
For gigabit, auto-neg is almost always recommended. Performance deteriorates when they try to force.