[mythtv-users] mythcomflag - how do I set nice level?

[Mark Knecht]

On 9/23/05, Ryan Steffes <rbsteffes at gmail.com> wrote:
>
>
> > >
> > They do not appear to be.
> >
> > ivtv0 = 22
> > ivtv1 = 17
> > eth0 = 20
> >
> > However ivtv1 is sharing with some part fo the chipset:
> >
> > dragonfly ~ # cat /proc/interrupts
> >            CPU0
> >   0:   14871236    IO-APIC-edge  timer
> >   1:      23821    IO-APIC-edge  i8042
> >   9:          0   IO-APIC-level  acpi
> > 12:     308115    IO-APIC-edge  i8042
> > 14:     187334    IO-APIC-edge  ide0
> > 15:         49    IO-APIC-edge  ide1
> > 16:     485287   IO-APIC-level  uhci_hcd:usb2, uhci_hcd:usb5,
> > i915 at pci:0000:00:02.0
> > 17:      57811   IO-APIC-level  ivtv1, Intel ICH5
> > 18:        109   IO-APIC-level  uhci_hcd:usb4
> > 19:        174   IO-APIC-level  uhci_hcd:usb3
> > 20:    8034881   IO-APIC-level  eth0
> > 22:      38977   IO-APIC-level  ivtv0
> > 23:          4   IO-APIC-level  ehci_hcd:usb1
> > NMI:          0
> > LOC:   14872124
> > ERR:          0
> > MIS:          0
> > dragonfly ~ #
> >
>
>
>  I was having a very similiar problem, which is why I asked.  For me, it
> wasn't just failing though it was resulting in lock ups.  The solution was
> to turn off APIC in the BIOS and it's been hunky dory since.
>

As a test I jsut switched video storage to my local drive and ran a 30
minute test run recording two programs. Both programs came out 29:55
second, basically perfect.

One difference I noted was while running this test top said that I was
98% idle. Sounds great. While running an identical 30 minute test
storing on my NFS drive top said I was 98% 'waiting'.

I think my problem resides somewhere in the NFS system. I also note
looking at the output of ifconfig that both the backend side and the
NFS server are logging thousand up thousand 'collisions'. I need to
fix that next.

Thanks,
Mark