i7 2600k
8G DDR3 RAM
RADEON HD 6990 4GB
800w PSU
Getting average fps of 25 - 50 kokan full server 100player
i'm i missing something or???
kudos to you
1920x1080, current CPU clock: 3.7GHZ.PLODDITHANLEY wrote:Resolution? How much overclock on your CPU?
I got a 980ti also, it sometimes dips to 50wikipa wrote: MoulinKiller
if you get fps drops on that sexy system you shouldn't even touch PR
nice setup you got there pal, you rook!!!
Seems to know what he's talking about.Games will not benefit that much by having 4 cores instead of two. Here's why.
Basic Game Engine: 1 Thread
The problem with graphics API like DirectX and OpenGL is that it must be runned on one thread, and one thread only. So a basic game engine will run all of the logic and render logic into a single thread. These engines will often use a time delta to synchronize the updating of the game world accordingly to the render FPS.
Ex.: libGDX, SDL
Update and Render Loops Game Engines: 2 Threads
These engines pose a clear separation between the update of the game world and its rendering. They will sometimes separate these 2 logics into 2 threads to gain a small performance gain but mainly asynchronous rendering. This means that the game can render at 400 FPS and the logic will still update at 60 FPS.
Ex.: Most high-end game engines, like Unreal, CryEngine or Frostbite
Physics thread: +1 to X Thread
Some games will like to put physics calculation in another thread so it doesn't mess with the updating or the rendering.
Networking: +1 to X Thread
Game with online gameplay will often use a separate thread because most networking engines are blocking, which means the thread will block until data is received.
Disk IO operations: +1 to X Thread
File management on large files can block a thread for a small amount of time, so most game engine will put disk IO operations on another thread.
Summary
Basicaly, most game engines will use 1 or 2 threads for the game's frame and will add some threads for other operations. But mostly, a game will only use 1 or 2 cores. If the game has heavy physics, like Frostbite engine for the BattleField series, then the game will start using more than 2 cores.
CPU thread optimisation
Mostly, a CPU will run different threads on different cores. But that may not always be the case. Like Joe Swindell said in the comments, games are not actually written to use cores, but when you write threads, you hope that they will run so that the CPU will distribute them to different cores.
Conclusion
What matters in the end is chosing the right CPU for the games you want to play or make. For small to medium games like Minecraft, then it is useless to buy a 4, 6 or 8 cores CPU. For high-end games, then 4 cores becomes the better option. If you want to program games, the more cores the better for compiling (depends on the compiler) but for the actual game, 2 cores is more than enough.
Cache P.S.
Yes, 4MB cache on 2 cores will be better than 6MB cache on 4 cores. But this is not the most important thing to look for on a CPU. It really comes down to the clock speed.
The only air cooled solution I can think of that actually works, would be an NH-D14, or later, which has kept my CPU below 80c when doing 1.4v overclocking before, but then again it comes down to other things like case cooling and whatnot.MaSSive wrote:That and the decent cooling system, which rules out any aircooled solution.
Btw single core Pentium can be compared in theory by single thread performance with Core i5/i7 but in practice its utter ****. Single thread app might benefit whle entire system might be hit by high core usage plummetning it to smitters, and actually causing severe performance decrease.
If you run only PR on the PC that would work, but what about the other '99' processes in the back?
Or, ya know... Maybe not?Spieler4 wrote:Maybe clients with high ping on server causes fps drops on other clients ??