Core parking? Hmm this is all new.
1
New Mb And Cpu = Fps Drop
Started by Contrabandit, Jul 01 2015 05:28 PM
28 replies to this topic
#21
Posted 08 July 2015 - 05:49 PM
#22
Posted 09 July 2015 - 06:06 PM
Goose, on 08 July 2015 - 05:29 PM, said:
sys_budget_streamingthroughput = 45119488 sys_LocalMemoryGeometryStreamingSpeedLimit = 44062 sys_LocalMemoryTextureStreamingSpeedLimit = 44062 sys_streaming_max_bandwidth = 44062
Thanks!
I have applied your settings other than changing (sys_streaming_CPU = 6) which i assume is for the amount of cores?
Are there any other setting in the user.cfg that might benefit my system that are not in there yet?
I'll take anything i can get
xWiredx, on 08 July 2015 - 05:43 PM, said:
I believe its either 1.28v or 1.3v. I won't go over the 1.3v hump, but as always with proper cooling going higher than that shouldn't be dangerous. I believe 1.3v or 1.35v was the max Intel recommended via the guide released by motherboard manufacturers on launch day.
I'll have to play around with the bios a bit.
I'm still learning all the setting, especially the relation with the cpu and uncore or NB (what ever you want to call it)
Also timings for mem seem to be more important than mhz with these chips, kinda like amd is/was..
i do know i can get it to 4.4ghz on 1.25v tho as i had it at that on my first WIN install
#23
Posted 10 July 2015 - 01:14 PM
Contrabandit, on 09 July 2015 - 06:06 PM, said:
I have applied your settings other than changing (sys_streaming_CPU = 6) which i assume is for the amount of cores?
Are there any other setting in the user.cfg that might benefit my system that are not in there yet? I'll take anything i can get …
Are there any other setting in the user.cfg that might benefit my system that are not in there yet? I'll take anything i can get …
Huh? I gave you the set I use for my hexacore, already.
Note how the number-line for placing threads on cores is "zero though five" …
#24
Posted 10 July 2015 - 02:54 PM
sys_budget_sysmem = 5120 sys_budget_videomem = 4096 sys_MaxFPS = 71 or something sys_budget_streamingthroughput = x * 1024 sys_LocalMemoryGeometryStreamingSpeedLimit = x sys_LocalMemoryTextureStreamingSpeedLimit = x sys_streaming_max_bandwidth = x r_GeomInstancing = 1 r_multiGPU = 0 r_silhouettePOM = 0 r_stereodevice = 0 r_UsePOM = 0 sys_budget_soundCPU = 5 r_WaterUpdateThread = 2 sys_streaming_CPU = 4 sys_TaskThread0_CPU = 0 sys_TaskThread1_CPU = 0 e_GsmCache = 1 q_ShaderWater = 0 r_FogShadows = 0 sys_limit_phys_thread_count = 0 p_num_threads = 6 e_AutoPrecacheCgfMaxTasks = 6 p_num_jobs = 6 r_ShadersAsyncMaxThreads = 6 sys_job_system_max_worker = 6
0-5? i dont see that
I see ( p_num_threads = 6 ) and ( sys_streaming_CPU = 4 )
also there are ( sys_TaskThread1_CPU = 0 ) and ( sys_TaskThread0_CPU = 0 )... which i also assume i could add 2,3,4,5
Could you clue me in to what these setting do, or link me to a directory with descriptions and values?
i swear im not trying to be a pain in the butt,
#25
Posted 10 July 2015 - 05:16 PM
The block with "r_WaterUpdateThread" is the named thread list, and talks about what cores you place named threads on; the last two blocks are full of unnamed thread-counts ("p_num_threads" need "sys_limit_phys_thread_count" to be zero in order to do it's job.)
;ca_thread0Affinity = type: int current: 5 ;sys_TaskThread2_CPU = type: int current: 4 ;sys_TaskThread4_CPU = type: int current: 2 ;ca_thread1Affinity = type: int current: 3 ;r_WaterUpdateThread = type: int current: 5 ;sys_main_CPU = type: int current: 0 ;sys_physics_CPU = type: int current: 1 ;sys_streaming_CPU = type: int current: 1 ;sys_TaskThread0_CPU = type: int current: 3 ;sys_TaskThread1_CPU = type: int current: 5 ;sys_TaskThread3_CPU = type: int current: 3 ;sys_TaskThread5_CPU = type: int current: 1is the standard list, with the three that often show a large load sorted first; Notice it assumes a hexacore, then gives certain thread(s) a core to themselves, and the rest are triple-loaded. I don't know what Crytek was thinkin', but they picked badly for MW: O.
#26
Posted 12 July 2015 - 08:35 PM
Goose, on 10 July 2015 - 05:16 PM, said:
;ca_thread0Affinity = type: int current: 5 ;sys_TaskThread2_CPU = type: int current: 4 ;sys_TaskThread4_CPU = type: int current: 2 ;ca_thread1Affinity = type: int current: 3 ;r_WaterUpdateThread = type: int current: 5 ;sys_main_CPU = type: int current: 0 ;sys_physics_CPU = type: int current: 1 ;sys_streaming_CPU = type: int current: 1 ;sys_TaskThread0_CPU = type: int current: 3 ;sys_TaskThread1_CPU = type: int current: 5 ;sys_TaskThread3_CPU = type: int current: 3 ;sys_TaskThread5_CPU = type: int current: 1
Can i add these to my user config?
With hyperthreading enabled would it be possible to have a value of 12 considering there are also 6 more logical cores? or should 6 suffice in settings
p_num_threads
I think that will be the last of my questions.
Thanks for the help everyone, especially Goose for all the explanations on the different code.
If any one has any more user.cfg lines they want to add you're more than welcome too
#27
Posted 12 July 2015 - 09:00 PM
Contrabandit, on 12 July 2015 - 08:35 PM, said:
With hyperthreading enabled would it be possible to have a value of 12 considering there are also 6 more logical cores? or should 6 suffice in settings
p_num_threads
Thus far Goose who also has a hyperthreading Hex has been unable to get MWO to address more than 6 threads.
I have MWO addressing all 8 threads on my FX-8350. But these are apple to oranges.
You can try it, and if you would, log the results.
#28
Posted 12 July 2015 - 09:15 PM
r_WaterUpdateThread = 2 sys_streaming_CPU = 4 sys_TaskThread0_CPU = 0 sys_TaskThread1_CPU = 0is all you want to type on for a hexacore. You were asking about the default listing.
sys_limit_phys_thread_count = 0 p_num_threads = 6 e_AutoPrecacheCgfMaxTasks = 6 p_num_jobs = 6 r_ShadersAsyncMaxThreads = 6 sys_job_system_max_worker = 6would also be good. Or maybe replace "6" with a "12" …
#29
Posted 12 July 2015 - 09:18 PM
Hyperthreading is "invisible" to Cryengine, so you can't boss around the named thread with it. The unnamed threads may or may-not care …
I still don't know if FX-Modules are also "invisible" …
I still don't know if FX-Modules are also "invisible" …
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users