Any chance for better cpu utilization?

[MSFSRonS]

Thanks, I didn’t know FS2020 used a Tile Based renderer.

From another thread: Post by Crunchmeister71

@Crunchmeister71

I posted the explanation below in another thread a while back to explain in the most layman terms how multitasking in a game works. Keep in mind games are a very linear process (if A then B) that don’t lend themselves well to multithreading like productivity workloads like video rendering. In that latter case, a set workload is divided up by how many CPUs / core / threads you have. There’s no logic dependency involved. 8 cores? Video is broken into 8 chunks and fed to all 8 threads that will process it independently in parallel. Pretty simple by comparison to a linear experience like a game.

[MortThe2nd]

Pretty sure Crunch’s explanation lines up with mine?

Anyways, The main thread syncing the workloads back up is something you mentioned as well, and is correct. You mentioning that without the main thread the CPU would become overloaded is wrong though.

Without the main thread the sim simply wouldn’t work, since it’s the core component of the workload.

[MSFSRonS]

Crunchmeister71 said “games are a very linear process (if A then B)”
You said “Tile based renderers do this all the time.”

You said:

@MortThe2nd

You mentioning that without the main thread the CPU would become overloaded is wrong though.

I said:

@MSFSRonS

If software programs could hit all 16 logical processors with commands simulltaneously, that would result in overload in the CPU. It could not handle it and would lockup, quit/freeze/shutdown.

[MortThe2nd]

I feel we’re just misunderstanding each other, so I’ll leave it at that.

[PacificSet90456]

@MSFSRonS

From “Tom’s Hardware”:

A thread is a virtual version of a CPU core. To create a thread, Intel CPUs uses hyper-threading , and AMD CPUs uses simultaneous multithreading, or SMT for short (they’re the same thing). These are both names for the process of breaking up physical cores into virtual cores (threads) to increase performance.

You should contact Tom’s Hardware and/or Microsoft to update the Task Manager Peformace tab to fix their “THREADS” label. Task Manager shows 2700 THREADS and Tom’s Hardware says that a thread is a virtual version of a CPU, both of these cannot be correct. The Task Manager Details tab needs to be looked as well. It shows that my MSFS has 170 threads. I doubt it is running on 170 virtual cores no matter how good hyperthreading is. And if Task Manager is wrong about an important detail like the number of threads (2700 vs. 24 or 16 is a huge difference), then other Task Manager performance items should be questioned.

[Crunchmeister71]

You clearly don’t have any grasp of what a thread is in its different contexts (hardware vs software) and are quoting stuff you don’t understand from (correct) 3rd party web sites out of context to back up your incorrect assumptions.

[MSFSRonS]

@PacificSet90456

I doubt it is running on 170 virtual cores no matter how good hyperthreading is.

Tsk Tsk

Uh, hyperthreading is an Intel term.
Uh, see my quote right above.

Per Intel, hyperthreading created two logical threads for each core.

My i9-9900k has 8 cores and 16 threads.

Your reference to the 2700 or 270 in this post are Software processes.

Granted, Task Manager does label them as Threads. But I think the inference is software.

My CPU has 16 threads. Period. Intel sells it as 16 threads.

If I really have 2700 threads running,
I should be minning. I’d be rich.
And flying a real Cessna CJ4 instead of posting on this forum.

[PacificSet90456]

Thank you for the clarification!

Someone (like Intel) should have Microsoft fix Task Manager. The incorrect use of Intel’s terminology makes Task Manager worthless. I’d really like to know what those 2700 threads are in Task Manager “Threads” is a key item for me when I do performance analysis. I look at the number of threads running on each core. Now this doesn’t make any sense at all.

I don’t think there are 2700 processes running. Here is another terminology issue. Windows assigns a “process id” to each .exe and service when the start executing. flightsimulator.exe has only one process id, not 170.

These terminology differences between Microsoft and Intel are becoming a nightmare!