Author Topic: Disk Control has never been implemented?  (Read 633 times)

Offline Gianluigi Salvi

  • New
  • *
  • Posts: 1
  • Gender: Male
Disk Control has never been implemented?
« on: February 07, 2019, 02:23:46 PM »
Around version 7

@BenYeeHua made a lot of very interesting proposal:

Quote
3.Monitoring the Disk and/or SATA controller usage/active time of the Processes
I found that most people getting better CPU performance then the Hard Disk, and they always care about Disk usage/active time.
If Process Lasso support Disk usage, the Windows user that is not using Windows 8+ Task Manager will love to see this feature.

4.Support restraint of the Processes that monopolize the Disk/controller.
As about, and I found that most stutter is caused by the Hard disk is monopolized by some heavy read/write process, like game patch/validate.
If Process Lasso support restraint of I/O monopolize Processes, it will be a good feature too. :)

5.Better Responsiveness of Process Lasso/GUI while I/O is getting monopolized
I always found that Process Lasso GUI is laggy while opening it from Tray Icon, while I/O is monopolized by other processes.
Maybe stop trimming Process Lasso and Process Governor, and lock the pages in RAM should be enough?
http://msdn.microsoft.com/en-us/library/windows/desktop/aa366895%28v=vs.85%29.aspx

You can find them here:
https://bitsum.com/forum/index.php/topic,4399.msg15542.html#msg15542

Did they were taken into account?



Offline edkiefer

  • Volunteer User Moderator
  • Member#
  • *****
  • Posts: 1669
  • Gender: Male
Re: Disk Control has never been implemented?
« Reply #1 on: February 07, 2019, 06:32:55 PM »
Around version 7

@BenYeeHua made a lot of very interesting proposal:

You can find them here:
https://bitsum.com/forum/index.php/topic,4399.msg15542.html#msg15542

Did they were taken into account?
Hi, Thanks for bringing that thread up, it shows how much PL has improved since then.
On the topic of Hrad disk/I/O restraint, PL does have now I/O priority and it can lower I/O priority when Probalance restrains a process (Under advanced settings).

That said, in my experience, it is a tough call to restraint on I/O because a lot of times you want I/O to go as fast as it can, cause it will probably be the slowest area of the system.

For example, say you got a program scanning HD (like AV) unless the CPU usage goes way high most times it be best to let it finish its scan and if the process does go high on CPU usage Probalance will handle that part.

So it can be tricky for the best thing to do here IMO.
« Last Edit: February 18, 2019, 09:30:56 AM by edkiefer »
Bitsum QA Engineer