Thanks that's exactly what i thought about those thingamabobs. Now to redesign the colour scheme of my setup :/
Let me do the laymans explanation of what some of these fancy things do.
Originally TCP was designed for unreliable low speed networks. The TCP software implementations on host systems require extensive computing power. Full duplex gigabit TCP communication could consume more than 80% of a 2.4 GHz Pentium 4 processor resulting in little or no processing resources left for the applications to run on the system. So what manufacturers have started doing is offloading UDP, TCP and ARP processing to the NIC hardware. A generally accepted rule of thumb is that 1 Hertz of CPU processing is required to send or receive 1 bit/s of TCP/IP. In other words, a server with TCP/IP offload can do more server work than a server without TCP/IP offload NICs. Because some functions, like Connection Establishment (SYN, SYN-ACK and ACK) can now happen on the NIC and not on the CPU you also find that less data has to travel between the CPU and the NIC. Less data = more processing for CPU to do CPU related stuff, instead of having to do network related stuff.
Multiqueue NICs provide multiple transmit and receive queues, allowing packets received by the NIC to be assigned to one of its receive queues. Each receive queue is assigned to a separate interrupt; by routing each of those interrupts to different CPUs/cores, processing of the interrupt requests triggered by the network traffic received by a single NIC can be distributed among multiple cores, bringing additional performance improvements in interrupt handling. Usually, a NIC distributes incoming traffic between the receive queues using a hash function, while separate interrupts can be routed to different CPUs/cores either automatically by the operating system, or manually by configuring the IRQ affinity. That way, taking the application locality into account results in higher overall performance, reduced latency and better hardware utilization, resulting from the higher utilization of CPU caches and fewer required context switches.
Now Jumbo frames...aka MTU size over 1500 bytes. Even though supported you actually need to set the MTU on your router to something like 9000 bytes, that basically means that the payload for each frame is 6 times more that usual. This will not improve INTERNET performance, but if you have to PCs and both have MTU set to 9000 bytes and you send a large file it will require less packets to be sent over the network to do the same work. So instead of sending 6000 packets it will send 1000. That's the simplest explanation. In reality there are a number of other factors to consider, and generally you don't want to fiddle with this unless you know what you're doing.