Hi all, my PC resources are nowhere near maxed out, nor am i seeing any single CPU core maxxed at 100% CPU. I know theres a few things i could do to reduce the the inserter count. Only in the last day or so my Pyanadons playthrough started dropping below 60. I also could get rid of YARM and Train trains without too much concern. I would''ve thought id see some sort of usage being capped (RAM/GPU/CPU etc) with fluctuations. Any tips on how to read what I'm seeing and possibly fix it (Pollution and Biters are off). I'm guessing this will not be the last time i have UPS issues in this playthrough.
#Trying to understand where the UPS bottleneck is. Any Help Appreciated.
1 messages · Page 1 of 1 (latest)
Discord shrunk the image....
Image attached: https://i.imgur.com/3miSNl0.jpeg
Entity Updates: https://i.imgur.com/RIUXsro.png
Graphics Updates: https://i.imgur.com/I2yJA9b.jpeg
Swap bottleneck to -> bottleneck lite
yarm should definitly go. some other smaller mods should be removed if you can, like nanobots for example.
after that you need to do a lot more work to recover ups from loader spam. For example in screenshot i can see chest -> loader->loader-> machine, when an inserter would have done job and at alot lower fee, unless, you really need throughput of a loader.
Similar with Pump spam, try to stay within pumpless flow rate and just use vanilla fluid mechanics.
no need to remove yarm, you can just reduce how fast it updates in the settings
That only reduce script time. There is still Gui cost and data part in Lua.
Sooner or later he has to remove it unless he wants to pay in update.
You could check if setting your video settings in the game to low would do anything since render time is quite high, but following pandana's suggestions is probably the best idea
both of those things have miniscule impacts on UPS
a GUI existing doesn't do anything, and data doesn't have any impact on UPS at all
the update time affects how often it updates the GUI, which is exactly what you would want to do to reduce UPS usage
He is breaking already 1.2ms in lua garbage.