will an i5 2500 quad core and a 560 gtx bottlekneck?
bottlekneck
um.. i like your question.. let us just review our database and we will be with you shortly.... ... ... Yes.. here it is sir, the answer to the the ultimate question is 42. yes sir we are quite sure it is 42. :)
very funny i just can stop laughing hahahahah......
dude that is mean hahahaha. anyway, there is always going to be a bottleneck regardless of what you do, you just want to minimize the gap between the fastest component and the slowest. so what is it that you need that computer for?
gaming
- Edited
As long as the CPU and GPU are not both performing the exact same task (at that point you are free to throw your GFX card away), a bottleneck means that the GTX560 is being starved for data, able to calculate faster, while the CPU is still stuck performing its own processor-dependent calculations (AI, or CPU physics, for example). As such, when the CPU is doing its calculations fast enough, then the GPU becomes the bottleneck. Since it's the primary determinant of framerates and performance, then it stops being commonly called bottleneck, and start being called performance, since the whole point is to let the GFX card flex its muscles. This is why when you increase the CPU speed / change the CPU beyond the CPU bottleneck, and move towards GPU "bottleneck", it makes no difference, except if CPU cache changes. And that difference is almost negligible.babum wrotedude that is mean hahahaha. anyway, there is always going to be a bottleneck regardless of what you do, you just want to minimize the gap between the fastest component and the slowest. so what is it that you need that computer for?
You've outdone yourself again, thanks for the great infos. I was gonna google "bottleneck", but I found yasamokapedia instead. :Dyasamoka wroteAs long as the CPU and GPU are not both performing the exact same task (at that point you are free to throw your GFX card away), a bottleneck means that the GTX560 is being starved for data, able to calculate faster, while the CPU is still stuck performing its own processor-dependent calculations (AI, or CPU physics, for example). As such, when the CPU is doing its calculations fast enough, then the GPU becomes the bottleneck. Since it's the primary determinant of framerates and performance, then it stops being commonly called bottleneck, and start being called performance, since the whole point is to let the GFX card flex its muscles. This is why when you increase the CPU speed / change the CPU beyond the CPU bottleneck, and move towards GPU "bottleneck", it makes no difference, except if CPU cache changes. And that difference is almost negligible.