Is it possible to assign which thread goes to a specific core?
|
07-18-2013, 10:18 AM
arwing92 Wrote:If the OS automatically chooses a core how come when I look at the task manager each of the 4 physical + 4 virtual cores is receiving load including the virtual cores (HT on)? If I recall correctly, this is due to the fact that the measuring period of Windows Task manager causes a bit of "delay" when you read its report. Windows' task scheduling is responsible for determining which threads run on which cores. By default, it's pretty jumpy; Dolphin's threads tend to switch back and forth between cores rapidly (in nanoseconds probably) as it does its processing. From the time Windows Task Manager measures processor usage at one point until it measures again at another point, Dolphin's threads may have jumped hundreds (if not thousands?) of times across various cores. Since these cores were used at one point by Dolphin's threads in some capacity, Windows Task Manager will report them as having been used (for the period it measured any way). Long story short, Windows does choose specific cores to run threads on, it switches so fast between them all, it only looks like a lot are being used at once. 07-18-2013, 05:13 PM
Code: start /affinity AA Dolphin.exe 07-19-2013, 02:35 AM
(This post was last modified: 07-19-2013, 02:40 AM by ExtremeDude2.)
I'm not sure how that would work on a computer with less than 8 threads (note that I don't know how many threads that the person you are talking to has)
Edit: Wouldn't 0A or 05 be better for 4 threads? Edit 2: You also can set affinity in task manager 07-19-2013, 03:39 PM
Talking to the OP. I'd set at least 3 cores so the no real work done here threads don't interfere with the rest assuming Windows is smart enough to do that. You'd put it in a batch file so you don't have to mess with task manager every time.
07-20-2013, 09:34 AM
Quote:That will get you lock threads to cores if that's you want.No, that's not the same thing. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)