| 1 |
On Tue, 2005-09-20 at 09:04 -0700, Mark Knecht wrote: |
| 2 |
> On 9/20/05, Daniel Gryniewicz <dang@g.o> wrote: |
| 3 |
> > On Tue, 2005-09-20 at 09:58 -0400, Billy Holmes wrote: |
| 4 |
> > > Mark Knecht wrote: |
| 5 |
> > > > Thanks. Yes, I've run ck-sources a few times in the past but not had |
| 6 |
> > > |
| 7 |
> > > when you run with ck-sources, others have found it's best to use |
| 8 |
> > > SCHED_ISO rather than SCHED_NORM (ck was patched with ISO support) - |
| 9 |
> > > which is like real time scheduling for users processes. From what I hear |
| 10 |
> > > it's easier to setup than the rt limits stuff (ie. it's automatic). |
| 11 |
> > |
| 12 |
> > Much more important is to run emerge as SCHED_BATCH. I do this, and it |
| 13 |
> > keeps emerge for effecting my interactivity (including skips in |
| 14 |
> > audio/video) at all. |
| 15 |
> > -- |
| 16 |
> > Daniel Gryniewicz |
| 17 |
> |
| 18 |
> Daniel, |
| 19 |
> This makes sense but I've never heard of doing this before. How |
| 20 |
> does one run emerge as a SCHED_BATCH process? |
| 21 |
> |
| 22 |
> None the less, when recording in Ardour I'll be doing a reasonable |
| 23 |
> amount of disk I/O. Not so much bandwitch - probably never more than |
| 24 |
> 5-10MB/S on large recordings, but still it's a large number of audio |
| 25 |
> files and therefore more disk seeking, etc., so I'll want the whole |
| 26 |
> disk subsystem working well. |
| 27 |
> |
| 28 |
> Thanks, |
| 29 |
> Mark |
| 30 |
> |
| 31 |
|
| 32 |
I do this: |
| 33 |
alias emerge='sudo schedtool -B -e /usr/bin/emerge' |
| 34 |
|
| 35 |
Obviously the sudo is unnecessary if you're root. You can use similar |
| 36 |
aliases to run things as SCHED_ISO, which I do for mplayer, for example. |
| 37 |
|
| 38 |
Daniel |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-amd64@g.o mailing list |
Archives