NOTICE: This forum is mostly an archive, though new posts are allowed. Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by BenYeeHua, June 16, 2013, 01:39:38 PM
Quote from: edkiefer on June 16, 2013, 01:57:47 PMyou have probalance enabled ?I don't see any priority lowering in log or yellow bar in graph .Edit: I am seeing low responsiveness too with CPUeater .
Quote from: edkiefer on June 17, 2013, 12:52:01 PMThe other thing I noticed is PL graph didn't match CPUeater graphs with responsiveness .How do you set up app to cut cores off if loaded to high . wouldn't you need a different cpu load level for trigger that to be effective ?
Quote from: edkiefer on June 17, 2013, 12:52:01 PMEdit: Duh, I never looked good enough it seems in ProBalance settings ,there is option to set cores to cut off .
QuoteHmm, have to think about this a bit, cutting core is double edge sword .
Quote from: jeremy collake on June 17, 2013, 02:36:52 PMI moved this over to Team Bitsum for now, while I fumble around with improving things. I will restore it when I have better answers!
Quote from: BenYeeHua on June 18, 2013, 01:19:20 AMNot a problem. ----I think you "might" adding a function to ProBalance, when ProBalance detect the responsiveness under 50%, unload one of the core and restraint the foreground processes when it don't help(if the lag is caused by foreground processes).
Quote from: edkiefer on June 18, 2013, 10:02:21 AMThinking about this , how does the responsive meter measure ? (input lag? ) on any system overall or per process .What I am driving at and have not tested for example you play some game, this 99% of time would be foreground as full screen is "mostly" default.Now in game and way its coded response is good, no input lag or anything . but now say you alt-tab the game and run some other app, you might find it laggy a bit .So not sure you should ever cripple or hold back foreground process, at least 90% of time IMO .
QuoteI have OT question with cpu priories, i/o, etc when app run . Does the app control this or does windows do it or both can .reason I run the graphic app MSI Afterburner and by default having it run at startup I noticed it always below normal, an lower i/o but if I start it manually it comes up normal, was wonder what controls this the app or windows is doing something on its own .PS: the app MSI AB is setup through task scheduler if that matters .
Quote from: edkiefer on June 18, 2013, 01:01:36 PMYes, I should of thought that out more, even games that use 4+ cores only end up using on avg "about" 50% of CPU and yes the graphic thread is the heaviest one .
Quote from: BenYeeHua on June 18, 2013, 11:16:21 PMAnd this is very sad....But I think with the PS4 Xbox One using that moar coar AMD, this situation will be reduced. And we might playing game with Ultrabook SmartPhone in the future. ----Anyway, back to the Topic.If "Responsiveness" is correct, we can using it to improve ProBalance.
Quote from: edkiefer on June 19, 2013, 06:59:25 AMYes, but remember it not that game developers are lazy or stupid it the very nature of that type of app that it needs to wait on data from one thread completion to next to start another . you can only parallel so much . The only thing they can do really is add or do more computational data to use up more , like better physic's , more advance calculations of damage , flight models (weapons) etc .
Quote from: edkiefer on June 19, 2013, 01:38:36 PMnight an day .My short test . I had Palemoon running , about 50 tabs in background .I start cpueater (PL not running ) . I then repeat opening a PDF file , which takes long time to start, even 2nd time (good 30sec ). response meter is in the 25-55 & .I then run PL and repeat above test, the PDF opens instantly and response meter is always/mostly 100%This is on win7 64bit, 3570k @4.0ghz and CPUeater was set to 12 threads .
Quote from: edkiefer on June 18, 2013, 10:02:21 AMThinking about this , how does the responsive meter measure ? (input lag? ) on any system overall or per process .
QuoteSo not sure you should ever cripple or hold back foreground process, at least 90% of time IMO .
QuoteI have OT question with cpu priories, i/o, etc when app run . Does the app control this or does windows do it or both can .reason I run the graphic app MSI Afterburner and by default having it run at startup I noticed it always below normal, an lower i/o but if I start it manually it comes up normal, was wonder what controls this the app or windows is doing something on its own .
Quote from: Persona Support on June 21, 2013, 04:58:39 PMThanks! That's no surprise, let me explain:Responsiveness thread MUST run in a specific very low priority.Previously the GUI was run in the HIGH priority class, and this prevents the responsiveness thread from running in that very low priority.Now it is ABOVE NORMAL, which means it can get lagged, but the responsiveness thread is right.Solutions:1. Raise the priority of some other individual threads of Process Lasso may allow it to return its previous level of responsiveness and kill that lag.2. Isolate responsiveness calculation in a separate process. I really don't want to do this.Hopefully, with some tuning, I can get this right!This is a 'secret' I have not revealed. It's real simple. Real elegant. I just can't bring myself to reveal it . It's nothing complex though. It's overall, not per-process. The monitoring thread (set at the right priority ), basically reports how much responsiveness it can get. That's as best I can do without giving it away.I may have misunderstood, but Process Lasso never does ... If a process is restrained, it'll be instantly restored as soon as it enters the foreground.Both can control it. The OS just uses defaults. When a process is launched by some component (e.g. Task Scheduler), it can inherit from its parent though, or sometimes have its priority set by its parent. Is that process launched by the Task Scheduler?EDIT: Ok, I just made some adjustments to the primary thread's priority. I'll do some testing, but I think this will help the lag in high loads, and not affect the responsiveness calculation. It'll be in .27 beta. Best of both worlds I hope.EDIT2: BTW, .27 was a database mistake that lasted for about a minute; the current is .25.
Quote from: edkiefer on June 21, 2013, 05:32:01 PMI think I posted it above, but yes it run from task scheduler .
Quote from: Persona Support on June 21, 2013, 05:48:55 PMSorry, I am in one of my speed-read modes today . Most application developers probably haven't noticed the Task Scheduler child process low I/O and memory priorities, or in other cases, perhaps it's appropriate. Few applications change their own priorities. Process Lasso sets its own priorities (all), to resolve that issue with Task Scheduler child processes having low priorities.