Sim speed slowed down to a crawl

[Cheesehead1964]

I'm simming the Dodgers starting in 1947. Historic rosters and minor leagues.


I'm simming a month at a time. In 1950, the simming has slowed down to where it took about a half hour to sim the last few games of the season.



Any thoughts as to what is going on? It seemed to really slow down when the rosters expanded. Previous seasons simmed fine.

[NoOne]

check # of threads being used -- file menu in game -> settings and expert tab, i think? few choices, you'll find it (not "game settings" or league settings) or 'settings' when ootp initially loads, but before you load a league.

make sure it is not >cpu cores.

some chips may be recognized as x2 cores, but it's not really x2 cores. intel calls it 'hyperthreading', if i recall. e.g. mine is 4 cores, but with hyperthreading it says 8.. but it still has 4, regardless. if i select "8" threads in ootp settings, it slows to a crawl.

sometimes 'default' will select the wrong # of cores in past. thought they amended that a couple years ago, though.

[Cheesehead1964]

Originally Posted by NoOne

check # of threads being used -- file menu in game -> settings and expert tab, i think? few choices, you'll find it (not "game settings" or league settings) or 'settings' when ootp initially loads, but before you load a league.

make sure it is not >cpu cores.

some chips may be recognized as x2 cores, but it's not really x2 cores. intel calls it 'hyperthreading', if i recall. e.g. mine is 4 cores, but with hyperthreading it says 8.. but it still has 4, regardless. if i select "8" threads in ootp settings, it slows to a crawl.

sometimes 'default' will select the wrong # of cores in past. thought they amended that a couple years ago, though.

Thanks much.


So I have an Intel Core i5-8250U 1.6 GHz 1.8 GHz processor


Number of Helper Threads is set at User Recommended (8).


Should I set it at 4? Or none?

[NoOne]

"4" is what you want. that chip has 4 physical cores.

https://ark.intel.com/content/www/us...-3-40-ghz.html

ignore the "thread" spec. that does not correlate to what ootp settings are mentioning.. .not exactly anyway.

i'd bet money that is the source of your problem.

[Cheesehead1964]

Originally Posted by NoOne

"4" is what you want. that chip has 4 physical cores.

https://ark.intel.com/content/www/us...-3-40-ghz.html

ignore the "thread" spec. that does not correlate to what ootp settings are mentioning.. .not exactly anyway.

i'd bet money that is the source of your problem.

Thanks much!

[Cheesehead1964]

Shoot. Still hanging up. Seems to manage my history replay where I'm replaying a season at a time as GM starting in 1903 (currently in 1939) without an issue.

It's hanging up on the my Dodger replay started in 1947. I go month to month managing the Dodgers. Seems to hang up in September.

[slugga27]

Originally Posted by Cheesehead1964

Shoot. Still hanging up. Seems to manage my history replay where I'm replaying a season at a time as GM starting in 1903 (currently in 1939) without an issue.

It's hanging up on the my Dodger replay started in 1947. I go month to month managing the Dodgers. Seems to hang up in September.

Have you tried restarting your computer? This has helped me tremendously when the game slows down.


Sent from my iPhone using Tapatalk

[Andy]

Originally Posted by slugga27

Have you tried restarting your computer? This has helped me tremendously when the game slows down.


Sent from my iPhone using Tapatalk

Such a simple thing, but crazy how often it works.

[NoOne]

Hangs in september? i bet it's the end of season stuff for MiL leagues / call-ups if those are around in 1947. you can look to spread it out per league or make it all happen on one day based on scheduels/start dates etc.

if it's localized to one time period, it's probably not completely avoidable. if it is specific days it slows down but not other days shortly after/before, this is likely the cause.

if not...

try to see what is different between the two leagues... try anything new?

if MiL is active in 1947 but not 1900, it could be this, but i doubt it would slow it down as much as you mention (before i saw specific september comment). check MiL stats and AI settings -- make sure it isn't set to 'force results' or similar checkbox verbage. that can make things a crawl (whole season, not 1 month).

if it's just processing related -- turn some thigns to ondemand - like pictures, and anything you can recreate with boxscores/gamelogs etc... it won't be lost and it'll generate so fast when you click you won't notice in most cases.. as opposed to thousands generated automatically that you'll never look at.

on demand wpa graphs instead of automatically creating them every single game, for example. typically the mouseover tip lets you know if it can be recreated from logs/boxscores and what is required to be enabled for that to occur.

stats and ai settings -- if you don't do much with mil, turn stats tracking down to "low detail" - has to be done for each mil league in dropdown selection box. even turn off awards or playoffs. something to think about for AAA and call-ups even if it doesn't solve problem.

edit: the threads settings may require a restart of the application... not likely a reboot of compuer, but not entirely unheard of, either.

[Cheesehead1964]

Thanks for all the replies.

Could be laptop related too. Running slow this morning, so I turned off many of the startup menu things that are running in the background. Seemed to help...

And yeah, restarted the computer several times. Always a good thing to try!

[NoOne]

hey, try "1" thread too... just in case... if the same results, pop it back to "4".

definitely don't use 8 for your cpu.

reducing startup junk is always a good idea. when my pc turns on win10 only uses 1.2-1.4gb of ram. that's with the 'large' ram footprint set in registry too. some sites will suggest turning that down, but it's just going to cause more work in long run due to extra swapping from page file to ram and whatever else. startup of <1gb is possible, but not necessarily helpful in that context.

services.msc - sort by startup type so "automatic" is all at top and also sort by 'running' after that for a quick glance at anything that isn't automatic, but is on.. turn off junk that isn't microsoft-related. e.g. if adobe reader is installed it has a service running constantly to check for updates... you can simply click update every once in a while, instead. not so important ot run 24/7. mozilla background service is total waste too - even uninstall that nonsense.

use common sense and don't turn off anything you can't tell exactly what it is -- preferably things related to your installs and not microsoft. although, disabling telemetry and some other stuff is totally fine too. i'm not a fan of superfetch/prefetch either. disabling prefetch will require a registry edit.

[jimmysthebestcop]

The setting is not asking about your cores. It is asking about your threads. Threads does not equal cores. Yes we can all agree on that.

But you wouldn't want to lower the games access to all of your threads. That advice doesn't really make much sense.

It shouldn't slow to a crawl unless it is set higher then your actual thread count.

[NoOne]

what ootp says in the settings and the exact definition of a thread are two different things.

one day i turned my 'intel hyperthreading' (w/e it is called) on and ootp was set to 'default', which then used "8" instead of "4," and my game took forever to sim one regular day. try it... go turn "ootp thread' above # of physical cores and see how it works out.

i'm not going to change the vocabulary of what he will see in the game. that'll just get confusing. maybe this was smoothed out in later patches. i have not tried since then. i was not the only person to have the problem. i've seen others make posts in teh forums in past years. this fixes it, regardless of the word used.

are you right? sure, but i'm not writing out why this is named that instead of the other thing in ootp settings, lol. simply saying match ootp setting to # of cores is easiest.

regardless, he left out a tidbit that was later revealed... it only happens in to the op in september. so, it's not related to this setting, anyway.

it should probably be called 'processes' which then have a number of threads. i guess? but ootp doesn't run as multiple processes. it also doesn't only have 1-8 threads allocated, lol.

i have "4" threads selected and look at what taskman says - 14 threads for ootp20:

[jimmysthebestcop]

I have 6 cores and 12 threads OOTP has always been set to default 12 threads. Never a problem with simming. Had it since OOTP 18.

Taskman thread column has to do with the OS and processes it runs and not the actual CPU/cores/hyperthreading lanes.

The OP might have had a different problem but seems like strange advice disabling threads for OOTP.

Hyper-threading should always be turned on. It was really only a feature on the i3 and i7 as the i5 was straight 4 cores and 4 threads without hyper threading.

Even the 9th gen i5 doesn't have hyper threading its 6 cores/6 threads. The i7 has hyperthreading thats why it costs way more.

AMD Ryzen uses SMT "Simultaneous multithreading". But same thing different name.

[NoOne]

hyperthreading is limited in what it can help and also slows down various other types of programs.

there are plenty of examples where it slows things down.

https://www.pugetsystems.com/labs/hp...rformance-578/

https://stackoverflow.com/questions/...ode-run-slower

https://www.bit-tech.net/reviews/tec...cpu-review/10/


maybe ootp is now programmed to make effecient use of hyper-threading, which was not he case initially. I went from ~3-4minutes per year simmed (at that time) to 15-30minutes or more - i can't recall exactly, but it was a huge and noticeable difference with the eye alone. i mention that this was in the past... that shoudl indicate the possibility of things being different now.

i also have a ~2010 cpu. there are so many factors invovled, and i didn't get specific. i merely said this can cause a severe slow down if number of threads in the ootp setting, which may or may not be fully definied by their choice of words, differed from # of actual cores. This is not a false statement. it's real and occured, and not just in my experience. you can find older threads where this did solve their problem.

if you try to 'pipe' a full load to one of those faux-cores, it'll create huge delays as something with <1/3rd the computational power is expected to do the same work in parrellel. that would be my best guess as to why, but i don't care why... i care that my sim times exploded exponentially. the syntax / proper vocabulary is irrelevant, lol.