https://bugs.kde.org/show_bug.cgi?id=376198

Mauro Carvalho Chehab <mchehab+...@kernel.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Mauro Carvalho Chehab <mchehab+...@kernel.org> ---
(In reply to yulinux from comment #5)
> With the latest changes from today (probably "dvbepg: optimize EPG
> duplicated entry handling" ?) it starts much faster:
> 
> $ date && ./kaffeine
> Do 16. Feb 14:01:14 CET 2017
> 16-02-17 14:01:15.139 [Info    ] Using built-in dvb device manager
> 16-02-17 14:01:15.825 [Info    ] Found dvb device : Realtek RTL2832 (DVB-T)
> 16-02-17 14:01:16.499 [Info    ] Found dvb device : Panasonic MN88473
> 
> 2 seconds for the total start is okay.
> 
> Without this change it was more than twice as long:
> $ date && ./kaffeine
> Do 16. Feb 13:55:14 CET 2017
> 16-02-17 13:55:17.792 [Info    ] Using built-in dvb device manager
> 16-02-17 13:55:18.480 [Info    ] Found dvb device : Realtek RTL2832 (DVB-T)
> 16-02-17 13:55:19.147 [Info    ] Found dvb device : Panasonic MN88473
> 
> I do no know why it is now not 12 seconds as described above any more, but
> that was the value measured last time. I also changed my DVBT device and
> there are some changes to the channels etc.
> 
> 
> With --debug it takes longer, as it prints so much out. More complete
> versions are attached.
> 
> One point is that kaffeine is reading EPG messages, although there are not
> scheduled recordings.

Hmm... it will actually read the EPG messages usually stored at:
    ~/.local/share/kaffeine/epgdata.dvb

That should be quicker, although, if I remember the code, it will pass though
the logic that detects duplicated events too, and discarding too old entries.

 That can
actually explain the start delay you had in the past version.

> But this is not a problem any more, as it is pretty
> fast now, just wanted to tell you. Anyway, for me this can bug report can be
> closed now.
> 
> But as visible in the attachments, there is nice progress: before there was
> like at least 4 seconds EPG stuff, now it's around 1 second.

Good news! I'll close this bug as FIXED. Please re-open if you still find
something weird there.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to