Reply to thread

Message

<blockquote data-quote="edsche" data-source="post: 580871" data-attributes="member: 28762">Re: InfoService v1.32 - 5 day weather/Feeds/Twitter on basic home [04-01-2010] *PLANNI have similar problems with other plugins, randomly the dialog menu is lagging like hell, don't know why it happens.Updating feeds should not make a big difference with the overall speed of MP, especially not with the beta. Also a lot of feeds should not make a big difference. I've added 8 feeds and i have no problem with the overall speed of MP, neither on my Dev PC nor on my HTPC. A little explanation how InfoService works: InfoService will check every 60 seconds if there is something to do. This means it will check if the refresh interval of Feed and/or Twitter and/or Weather is timed out. This is no big calculation and of course no big performance consumer. If the refresh interval is timed out, InfoService will try to update the timed out service. After finished update, it begins again to listen if there is something to do.... The update process of the 1.32 version takes cpu time from MP. The newer beta uses his own CPU time.</blockquote>

[QUOTE="edsche, post: 580871, member: 28762"] [b]Re: InfoService v1.32 - 5 day weather/Feeds/Twitter on basic home [04-01-2010] *PLANN[/b] I have similar problems with other plugins, randomly the dialog menu is lagging like hell, don't know why it happens. Updating feeds should not make a big difference with the overall speed of MP, especially not with the beta. Also a lot of feeds should not make a big difference. I've added 8 feeds and i have no problem with the overall speed of MP, neither on my Dev PC nor on my HTPC. A little explanation how InfoService works: InfoService will check every 60 seconds if there is something to do. This means it will check if the refresh interval of Feed and/or Twitter and/or Weather is timed out. This is no big calculation and of course no big performance consumer. If the refresh interval is timed out, InfoService will try to update the timed out service. After finished update, it begins again to listen if there is something to do.... The update process of the 1.32 version takes cpu time from MP. The newer beta uses his own CPU time. [/QUOTE]

Verification