Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] High CPU usage of VDR 1.1.11
- To: vdr@linuxtv.org
- Subject: [vdr] High CPU usage of VDR 1.1.11
- From: Oliver Endriss <o.endriss@gmx.de>
- Date: Sun, 29 Sep 2002 23:32:27 +0200
- Content-transfer-encoding: 8bit
- Content-type: text/plain; charset="iso-8859-1"
- Organization: ESCAPE GmbH EDV-Loesungen
- Reply-to: vdr@linuxtv.org
- Sender: vdr-bounce@linuxtv.org
- User-agent: KMail/1.4.1
Hi,
I just tested VDR 1.1.11 on a Pentium I 233 MMX.
This is a slow machine, but there have never been any problems.
(With VDR 1.0.4 peak CPU usage is about 25% during recording.)
With VDR 1.1.11 and NEWSTRUCT driver, it is impossible to create a good recording.
CPU usage is at 100% and there are lots of error messages in the syslog:
|Sep 29 20:45:05 orion vdr[11927]: timer 1 start
|Sep 29 20:45:16 orion vdr[11927]: record /video/@RTL__/2002-09-29.20:45.50.99.rec
|Sep 29 20:45:18 orion kernel: buffer empty
|Sep 29 20:45:25 orion last message repeated 4 times
|Sep 29 20:45:26 orion vdr[11940]: ERROR: ring buffer overflow (61 bytes dropped)
|Sep 29 20:45:26 orion vdr[11940]: ERROR: ring buffer overflow (188 bytes dropped)
|Sep 29 20:45:29 orion last message repeated 902 times
|Sep 29 20:45:29 orion vdr[11939]: ERROR: skipped 127 byte to sync on TS packet
|Sep 29 20:45:29 orion vdr[11940]: ERROR: ring buffer overflow (188 bytes dropped)
|Sep 29 20:45:29 orion vdr[11940]: ERROR: ring buffer overflow (61 bytes dropped)
|Sep 29 20:45:29 orion vdr[11940]: ERROR: ring buffer overflow (188 bytes dropped)
|Sep 29 20:45:32 orion last message repeated 727 times
|...
|Sep 29 20:45:47 orion vdr[11940]: ERROR: ring buffer overflow (188 bytes dropped)
|Sep 29 20:45:50 orion last message repeated 670 times
|Sep 29 20:45:50 orion vdr[11939]: ERROR: skipped 127 byte to sync on TS packet
|Sep 29 20:45:50 orion vdr[11940]: ERROR: ring buffer overflow (188 bytes dropped)
|...
When I stop recording CPU usage is still at 100%, until I switch channels.
Then it drops to normal (< 5%).
I get similar results with the old driver + time-shifting firmware.
After I disabled "#define DVB_DRIVER_VERSION 2002090101 //XXX+" VDR seems to
work normal no watter which driver/firmware is being used.
Before I start some debug sessions:
Is it normal that the new code needs so much horse power?
Oliver
--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.
Home |
Main Index |
Thread Index