Originally Posted by CNCoRIDDoR
Ok I'll go on for about 4 more hours. Do you guys know how to tell signs of bottle necking?
There's a difference between different definitions of bottlenecking. If you mean the correct (according to me) definition, then no.
Correct definition: A bottleneck is a result of one piece of hardware not permitting another to function at its full capacity in any circumstance.
Correct definition example: You have a SATA3 SSD plugged into a SATA2 port on your motherboard. The SATA2 port is bottlenecking your SSD - you can never get faster than SATA2 speeds out of it, even though the SSD could perform much better.
Solution: Plug the SSD into a SATA3 port, possibly requiring a motherboard upgrade.
HOWEVER, lots of people use a different definition of bottlenecking. According to me, the incorrect one.
Incorrect definition: A bottleneck is when one piece of hardware is not performing up to its maximum potential in a specific task because another piece of hardware can't keep up.
Incorrect definition example: You have a Radeon 5850, which is capable (or nearly so) of displaying SC2 at maximum graphics settings at your monitor's resolution & maximum refresh rate (best possible image quality at maximum effective FPS), however, because your CPU (an overclocked i7-3770K) cannot run SC2 at maximum FPS (your monitor's refresh rate) when large armies are on the field, you aren't getting maximum theoretical potential out of your 5850.
The difference is that the second (incorrect) definition is task-specific. Sure in SC2, there's a CPU "bottleneck," but for the vast majority of games it's the opposite: your i7-3770K is more than enough power to do everything you want other games to do, but your 5850 will hold you back.
So to answer your question:
Your system has no bottlenecks (first, correct definition).
Your question is meaningless without giving us context in terms of what software you're running (second, more common but incorrect definition).
The reason the term bottlenecking bugs me so much is that people hear they have a bottleneck (incorrect definition) and assume they have a bottleneck (correct definition) and that there are magic hardware configurations that will never have bottlenecks (incorrect definition) when that outcome is, in fact, impossible.