Reply to thread

Message

<blockquote data-quote="Micropolis" data-source="post: 519147" data-attributes="member: 96567">HTPCInfo for MediaPortal v0.7.0Hi Joz,thx fo your experiments and posted results of this. I my opinion, this is useful for people, if performance issues are detected.I had also make some stress tests (e.g. with CPUStress from the Windows Resource Kit) and my mediaportal installation/configuration in combination with HTPCInfo was stable enough, also with 99% CPU usage.Some background informations about the architecture of HTPCInfo:<ul>
<li data-xf-list-type="ul">There are two different types of properties: fixed properties (e.g. machine informations - these functions will be called only at startup) and variable properties (e.g. performance counter).</li>
<li data-xf-list-type="ul">To update these variable properties, a combination of timer and background worker (medium priority) is used. Currently the timer checks every second, if it is possible and required to update the informations.</li>
<li data-xf-list-type="ul">You can change the update speed manually, for this please insert &quot;&lt;entry name=&quot;UpdateSpeed&quot;&gt;1000&lt;/entry&gt;&quot; (1000 milliseconds = 1 sec) to the HTPCInfo section in mediaportal.xml and change the value, e.g. 5000. After restarting all properties will only be refreshed every 5 seconds.</li>
</ul>Anyway, the idea for my hint from #130 was only to say: new features - no problem, but we must estimate, if a function is good/bad for MediaPortal performance. And again: The user has the chance to customize it in many ways. That's it.Cheers, Micropolis</blockquote>

[QUOTE="Micropolis, post: 519147, member: 96567"] [b]HTPCInfo for MediaPortal v0.7.0[/b] Hi Joz, thx fo your experiments and posted results of this. I my opinion, this is useful for people, if performance issues are detected. I had also make some stress tests (e.g. with CPUStress from the Windows Resource Kit) and my mediaportal installation/configuration in combination with HTPCInfo was stable enough, also with 99% CPU usage. Some background informations about the architecture of HTPCInfo: [LIST] [*]There are two different types of properties: fixed properties (e.g. machine informations - these functions will be called only at startup) and variable properties (e.g. performance counter). [*]To update these variable properties, a combination of timer and background worker (medium priority) is used. Currently the timer checks every second, if it is possible and required to update the informations. [*]You can change the update speed manually, for this please insert "<entry name="UpdateSpeed">1000</entry>" (1000 milliseconds = 1 sec) to the HTPCInfo section in mediaportal.xml and change the value, e.g. 5000. After restarting all properties will only be refreshed every 5 seconds. [/LIST] Anyway, the idea for my hint from #130 was only to say: new features - no problem, but we must estimate, if a function is good/bad for MediaPortal performance. And again: The user has the chance to customize it in many ways. That's it. Cheers, Micropolis [/QUOTE]

Verification