Summary: | PORTAGE_NICENESS only encapsulates nicess of compilation. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Olliver Schinagl <oliver> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Olliver Schinagl
2005-02-22 05:28:14 UTC
Portage does run absolutely everything at whatever nice level you specify after its first initialization. The problem you are having is related to lack of custom I/O priorities in the kernel. Google for information about anticipatory schedule, CFQ scheduler and time-sliced CFQ scheduler. There are indeed 3 I/O shedulers hidden under 'blockdevices'. They where all 3 enabled. The problem was much 'simpler' then that. nVidia IDE chipset drivers didn't play nice. Selecting different drivers for the nForce2 fixed the unzipping delay. Thanks anyhow! |