Reply to thread

Message

<blockquote data-quote="lugiber" data-source="post: 13447" data-attributes="member: 10335">On my 3ghz (intel with hyperthreading) cpu at work lcdsmartie uses about 6% cpu when media portal is turned off and 33% when it is running. Media portal uses about 2% when smartie is turned off and 16% with smartie is turned on. This definetly has to do with my config using $dll(LCDMediaPortal.dll,5,#id,) to change screens. Because when i remove all the 18 referenses to this function the cpu consumption returns to normal. I know nothing about programming so this is a stab in the dark. Could this be caused by the fact that smartie requests the &quot;#id&quot; from your plugin which requests the #id from the external control plugin which in turn requests the #id from media portal?Could your plugin be set to &quot;deny&quot; requests for #ids that are not active? Or perhaps &quot;remember&quot; which screen is active so that the #id requests can be kept to a minimum. The cpu consumption (in my opinion) clearly has to do with too many #id requests. Sorry if these suggestions are stupid, but remember i can't do any programming./Peter</blockquote>

[QUOTE="lugiber, post: 13447, member: 10335"] On my 3ghz (intel with hyperthreading) cpu at work lcdsmartie uses about 6% cpu when media portal is turned off and 33% when it is running. Media portal uses about 2% when smartie is turned off and 16% with smartie is turned on. This definetly has to do with my config using $dll(LCDMediaPortal.dll,5,#id,) to change screens. Because when i remove all the 18 referenses to this function the cpu consumption returns to normal. I know nothing about programming so this is a stab in the dark. Could this be caused by the fact that smartie requests the "#id" from your plugin which requests the #id from the external control plugin which in turn requests the #id from media portal? Could your plugin be set to "deny" requests for #ids that are not active? Or perhaps "remember" which screen is active so that the #id requests can be kept to a minimum. The cpu consumption (in my opinion) clearly has to do with too many #id requests. Sorry if these suggestions are stupid, but remember i can't do any programming. /Peter [/QUOTE]

Verification