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. -- Ontv uses lots of CPU and memory when updating tv listings https://bugs.launchpad.net/bugs/191700 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
