Originally posted by kwahoo
View Post
We have determined through testing that the "ondemand" governor (which is default, and which you have) seems to have some bugs and causes the erratic behavior that you see on your FPS graph. It appears as if the governor and scheduler interact in a weird way so that governor downclocks less used cores, but then the scheduler moves the main thread to that underclocked core, which the governor then clocks back, etc ad nauseam. We have contacted kernel devs, most notably developers from Intel that are working on that area, but they seem to still be looking into this.
The only workaround that we can come up from application side was to set strict affinity for each thread.
Ultimately, it is best if you switch to using the "performance" governor.
The only workaround that we can come up from application side was to set strict affinity for each thread.
Ultimately, it is best if you switch to using the "performance" governor.
Comment