Ontv uses lots of CPU and memory when updating tv listings
Bug #191700 reported by
Wouter Stomp
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ontv (Debian) |
Fix Released
|
Unknown
|
|||
ontv (Ubuntu) |
Confirmed
|
Undecided
|
Olof Kindgren |
Bug Description
Binary package hint: ontv
Ontv uses a lot of CPU and memory when it updates the tv listings. According to the system monitor, it uses up to 60% cpu, severely slowing down the system and up to 200mb of memory. Even worse it keeps using 200mb of memory after it has finished updating.
Changed in ontv: | |
status: | Unknown → New |
Changed in ontv: | |
status: | New → Confirmed |
Changed in ontv (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Just wanted to comment on how this works. When updating listings two shell (which are not part of OnTV) scripts are executed, the configured grabber and tv_sort. I think these are the ones responsible for the increased cpu usage, especially tv_sort. It would be nice if we could get rid of that one because it's really only used to fill in missing stop_times in the grabbed xmltv file. We should be able to do this ourself when loading the data. I don't have time to look into this but patches are of course welcome. :-)
About the memory. Are you looking at resident memory? Because that's really what's interesting in this case. It's true that the applet uses a lot of memory but that's because it's keeping all listings in memory. If you want to bring it down you could use the --days option for the grabber. Did some quick measurements, when starting up it's using 49mb, after one update, 88mb, second update 99mb. I think the biggest reason for the increase is Python which is known for being bad at releasing memory.