On Tue, 2005-09-20 at 09:04 -0700, Mark Knecht wrote: > On 9/20/05, Daniel Gryniewicz <[EMAIL PROTECTED]> wrote: > > On Tue, 2005-09-20 at 09:58 -0400, Billy Holmes wrote: > > > Mark Knecht wrote: > > > > Thanks. Yes, I've run ck-sources a few times in the past but not had > > > > > > when you run with ck-sources, others have found it's best to use > > > SCHED_ISO rather than SCHED_NORM (ck was patched with ISO support) - > > > which is like real time scheduling for users processes. From what I hear > > > it's easier to setup than the rt limits stuff (ie. it's automatic). > > > > Much more important is to run emerge as SCHED_BATCH. I do this, and it > > keeps emerge for effecting my interactivity (including skips in > > audio/video) at all. > > -- > > Daniel Gryniewicz > > Daniel, > This makes sense but I've never heard of doing this before. How > does one run emerge as a SCHED_BATCH process? > > None the less, when recording in Ardour I'll be doing a reasonable > amount of disk I/O. Not so much bandwitch - probably never more than > 5-10MB/S on large recordings, but still it's a large number of audio > files and therefore more disk seeking, etc., so I'll want the whole > disk subsystem working well. > > Thanks, > Mark >
I do this: alias emerge='sudo schedtool -B -e /usr/bin/emerge' Obviously the sudo is unnecessary if you're root. You can use similar aliases to run things as SCHED_ISO, which I do for mplayer, for example. Daniel -- gentoo-amd64@gentoo.org mailing list
