Jimmy Wilkinson Knife wrote:
On Sun, 21 Oct 2018 02:59:17 +0100, Paul wrote:

Jimmy Wilkinson Knife wrote:


I think it did stay lit, but that could be paging as it only has 4GB
RAM.

Correction - very little disk activity, 43% CPU usage (of 4 cores).


They recommend doing a "Save" first, then "Exit" here.

https://forums.thesims.com/EN_US/dis...rever-to-close


The purpose of doing a test like that, is to see if the
thing is tasked with exiting only, it can do that in
a reasonable period of time.

I always save then exit, and yes it takes ages.

cd C:\Program Files (x86)\Steam\steamapps\common\The Sims 3\Game\Bin\
start /affinity 3 TS3W.exe

"The game has thread-pool issues with more than 2 cores.
If you prefer playing at 60 fps, whatever."

When you saw 43% CPU usage on a quad core, it can certainly
be railed on two cores, but smeared over four cores.

*******

If you feel unsure about the usage of affinity, and
don't want to adjust affinity from Task Manager, the
Boot Manager in Windows should also have the option
to limit cores. Purely as an experiment, you could
drop the machine to two cores at boot time, and
run the game for a test that way. If it shuts down
faster under those conditions, it could be that
"thread-pool issue" mentioned above. But it would
have to fork one hell of a lot of threads, to need
minutes to clean up afterwards. If each thread was
actively working on something and refused to quit,
it might be a different matter. I didn't think threads
were that hard to kill. Threads are lighter in weight
than a full process, and should be under the complete
control of the boss task. I don't really know if there's
a way that a thread pool can "go nuts".

On Win2K or WinXP, it was the "NUMPROC" option. Which gives
a search term to use for Windows 10. The Intel page is
for the boot.ini era.

https://software.intel.com/en-us/art...windows-system

And this is an example of a Vista/W7/W8/W10 command
to limit cores. You can run the commands from an
Administrator Command Prompt window.

https://www.geoffchappell.com/notes/...er/numproc.htm

bcdedit === review current settings. So you know what
it should look like later.

bcdedit /set numproc 2 === limit number of processor cores

bcdedit

bcdedit /deletevalue {default} numproc === can remove it entirely to
return system to original
condition.

Programs themselves can set their own affinity. If EA/Maxis
knew there was a problem, they could patch the product
so it set affinity when necessary.

An example of a program that set its own affinity, was
DScaler (a program that runs a WinTV card). It sets
affinity to two particular cores, in the hope the two
processes the program uses, will never run on the same
core. Doing that, was supposed to prevent the processes
from competing with one another. When you pin tasks
like that, the scheduler will still try to even the
load out on all cores, and the setting doesn't "exclude"
other programs from running on the cores in question.

HTH,
Paul