In few weeks i will change my i5 to i7-3610QM when I will find one a bit cheaper (used one maybe), and I will give You guys know about TW quad core performance
I think you will see better performance when switching from a hyper threaded Dual Core CPU to a hyper threaded Quad Core CPU. If you want to do a fair comparison, use ThrottleStop to slow down your new Core i7 so it runs at the same speed as your old Core i5. If your game plays better on your Core i7 at the same speed as your Core i5 runs at, that would prove that the extra cores really do make a difference. When you get your new CPU send me a PM if you need some help with this test.
If anyone else has this game and a Quad Core CPU, go into the bios and turn off 2 cores and you can do some testing that way to see if extra cores makes a difference or not. You can also try using msconfig to disable half of a Quad Core CPU for testing purposes.
How many of those quadcores were running faster than the dual cores?
The first test on the Russian website I posted equalized all of the CPUs at 3000 MHz so they could do a fair, apples to apples, comparison. Their testing showed a clear improvement when going from 2 cores, to 2 cores with hyper threading to 4 cores. The Russian testing showed no performance increase when going from 4 cores to 4 cores with hyper threading and the bit-tech graph showed the same thing.
The bit-tech graph does not show any Dual Core CPUs with hyper threading. It does show larger percentage increases in FPS compared to the Russian testing when overclocking from 3.4 GHz to 5.0 GHz but this is irrelevant to crazydawid. He has a laptop and is considering getting a Quad Core CPU that in game will run at most 10% faster compared to his Core i5. Just an opinion but I think a 100% increase in the number of cores is going to make a bigger difference in FPS compared to a 10% increase in MHz.
The graphs that show the load concentrated on the first core or first thread are interesting. I am more of a programmer than a gamer so I decided to modify my i7 Turbo GT program that I wrote a few years ago. It was just a quick edit but now it is able to precisely log the load on each thread.
i7 Turbo GT - Version 1.4
https://www.sendspace.com/file/70ciqi
If anyone that plays Rome II wants to do some testing, run i7 Turbo GT and check off the Log option. Go play the game for a while and when finished, exit i7 Turbo GT and attach the log or post the data somewhere like
www.pastebin.com
By monitoring each thread, it should be easier to see how bad this overloading the first thread problem really is.
Slightly off topic but here is a look at the data this program can record.
Code:
DATE TIME PEAK CMULTI STDEV LOAD% C0%_0 C0%_1 C0%_2 C0%_3 C0%_4 C0%_5 C0%_6 C0%_7 NOTES
12/03/2014 23:57:21 33.393 32.948 0.370 1.14 4.26 0.26 0.54 0.75 2.01 0.19 0.59 0.54
12/03/2014 23:57:22 33.665 33.248 0.262 0.30 0.51 0.07 0.48 0.27 0.43 0.05 0.28 0.29
12/03/2014 23:57:23 33.614 33.221 0.274 0.47 0.66 0.08 1.62 0.19 0.30 0.04 0.33 0.56
12/03/2014 23:57:24 33.803 33.241 0.364 0.38 0.55 0.05 0.33 1.16 0.38 0.12 0.22 0.25
12/03/2014 23:57:25 33.546 33.126 0.276 0.55 0.90 0.18 0.51 0.59 0.66 0.21 0.49 0.86
12/03/2014 23:57:26 33.706 33.204 0.259 0.32 0.59 0.07 0.30 0.16 0.48 0.16 0.40 0.39
12/03/2014 23:57:27 33.697 33.333 0.184 0.31 0.55 0.05 0.35 0.16 0.29 0.22 0.53 0.32
12/03/2014 23:57:28 33.782 33.267 0.254 0.30 0.48 0.06 0.33 0.18 0.46 0.13 0.45 0.26
12/03/2014 23:57:29 33.698 33.192 0.269 0.27 0.57 0.08 0.31 0.13 0.33 0.04 0.44 0.29
12/03/2014 23:57:30 33.742 33.309 0.273 0.38 0.77 0.12 0.51 0.41 0.53 0.08 0.35 0.26
12/03/2014 23:57:31 33.760 33.302 0.205 0.28 0.52 0.04 0.36 0.15 0.50 0.06 0.37 0.26
12/03/2014 23:57:32 33.248 32.744 0.541 4.45 18.32 0.92 1.82 1.04 3.57 0.39 5.98 3.59 Move_Mouse_Test
12/03/2014 23:57:33 33.499 32.806 0.556 7.60 29.68 2.53 2.34 1.93 5.12 0.42 9.60 9.17
12/03/2014 23:57:34 33.688 32.900 0.571 5.58 25.68 1.89 2.69 1.80 4.66 0.51 1.48 5.91
12/03/2014 23:57:35 33.553 33.082 0.317 6.78 27.58 2.01 3.78 2.45 2.26 0.45 1.79 13.94
12/03/2014 23:57:36 33.434 33.052 0.305 7.02 27.28 1.70 4.30 2.42 2.15 0.83 4.22 13.24
12/03/2014 23:57:37 33.182 32.664 0.327 7.25 26.37 1.27 15.18 3.04 2.02 0.18 1.13 8.81
12/03/2014 23:57:38 33.189 32.925 0.138 3.54 11.76 0.51 6.49 2.41 1.10 0.27 1.68 4.07
12/03/2014 23:57:39 33.674 33.242 0.254 0.51 0.50 0.24 0.42 1.41 0.37 0.11 0.49 0.54 Test_Finished
12/03/2014 23:57:40 33.744 33.322 0.238 0.33 0.67 0.07 0.26 0.38 0.34 0.18 0.41 0.30
12/03/2014 23:57:41 33.662 33.285 0.189 0.29 0.54 0.06 0.36 0.21 0.44 0.12 0.32 0.26
12/03/2014 23:57:42 33.562 33.172 0.199 0.35 0.64 0.12 0.48 0.21 0.53 0.15 0.36 0.31
12/03/2014 23:57:43 33.711 33.285 0.218 0.26 0.43 0.05 0.44 0.15 0.34 0.12 0.31 0.26
12/03/2014 23:57:44 33.835 33.285 0.252 0.29 0.59 0.06 0.42 0.20 0.33 0.12 0.36 0.26
12/03/2014 23:57:45 33.662 33.302 0.282 0.42 0.61 0.07 0.23 0.41 1.12 0.12 0.48 0.35
12/03/2014 23:57:46 32.958 32.294 0.587 1.47 2.62 0.49 1.05 0.62 1.11 0.37 4.48 1.04
12/03/2014 23:57:47 33.741 33.225 0.331 0.27 0.65 0.07 0.25 0.26 0.31 0.05 0.29 0.29
12/03/2014 23:57:48 33.756 33.249 0.270 0.28 0.62 0.06 0.33 0.22 0.35 0.05 0.32 0.30
12/03/2014 23:57:49 33.722 33.261 0.251 0.28 0.57 0.05 0.32 0.17 0.51 0.06 0.26 0.27
12/03/2014 23:57:50 33.646 33.429 0.178 0.48 1.34 0.09 0.38 0.36 0.97 0.13 0.33 0.26
12/03/2014 23:57:51 33.751 33.326 0.189 0.28 0.50 0.08 0.34 0.19 0.44 0.12 0.27 0.26
12/03/2014 23:57:52 33.820 33.298 0.290 0.26 0.42 0.05 0.23 0.12 0.58 0.13 0.27 0.25
12/03/2014 23:57:53 33.735 33.299 0.199 0.26 0.59 0.06 0.25 0.14 0.38 0.11 0.33 0.26
You can see how before I start moving the mouse on my laptop, the CPU is very calm across all 8 threads.
Simply using the track pad and moving the mouse around in circles creates a huge CPU load which is concentrated on the first thread and there is also a lot of load that ends up on the last thread. This mostly proves that Elan needs to get their head out of their butt and release some better drivers that do not use the CPU excessively to poll the track pad. It should not take billions of CPU cycles to determine if someone moved the mouse using the track pad.
Hopefully this tool might help someone understand Rome II better. It would be even better if the programmers of Rome II used tools like this so they don't lock everything to the same core. That is a sign of old school programming from the single core era.