|
Size: 591
Comment:
|
Size: 671
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| If you want to do something that has approx. 1000 times more relavance than improving CPU schedulers by some statistically insignificant amount, then please solve the following practical issues: | If you want to do something that has approx. 1000 times more relevance than improving CPU schedulers by some statistically insignificant amount, then please solve the following practical issues: |
| Line 4: | Line 4: |
| * Prevent disk i/o intensive apps from blocking other apps that only do limited disk i/o. Again, we need some class or hierarchy structure to collect the statistics reliably. | * Prevent disk i/o intensive apps from blocking other apps that only do limited disk i/o. Again, we need some class or hierarchy structure to collect the statistics reliably. Please note: AFAIK current disk io schedulers are only "disk input schedulers". |
If you want to do something that has approx. 1000 times more relevance than improving CPU schedulers by some statistically insignificant amount, then please solve the following practical issues:
- Prevent memory hungry apps from forcing other apps (eg. sshd) into deep swap. AFAIK setrlimit does that on a per-process level. We need a per-class or per-process-hierarchy level.
- Prevent disk i/o intensive apps from blocking other apps that only do limited disk i/o. Again, we need some class or hierarchy structure to collect the statistics reliably. Please note: AFAIK current disk io schedulers are only "disk input schedulers".