HTPCInfo plugin v1.15.0 for MediaPortal 1.3.0 and higher (3 Viewers)

[joz]

Please be aware, that actually I must find a way to support needed functionalities and to develop a plugin, which cannot allocate all CPU/Memory resources. This is a small way, but in my opinion it is possible and usable for HTPCs with appropriate facilities. If a user does not want to use some functionalities, it is helpful and recommended to switch off this in the configuration dialog.

I understand, adding functionality will also demand more from the system. Normally this is not really a problem because most plugins just take up CPU time when you are in the plugin however with HTPC Info this is different since variables are accessible through out.
Would it be somehow possible (stop me if I'm asking too much here ) to configure which variables are accessible where? So on that basis it could save some system resources when you are not in the plugin, because the plugin has to monitor less? Not sure if that at all works like that (I think it should). Inside the plugin all variables can then be made accessible, on a global scale users can limit it?

Keep saying it, but also can't say it enough again!

 

[Zapp]

StreamedMP skin files?

Hmm, I can't see that there is any skin files for StreamedMP in v0.7.0!

Am I supposed to get that from the StreamedMP installation or from the HTPCinfo installation?

/Jonas...

 

[joz]

Just look here

 

[Micropolis]

HTPCInfo plugin for MediaPortal v0.7.0

I understand, adding functionality will also demand more from the system. Normally this is not really a problem because most plugins just take up CPU time when you are in the plugin however with HTPC Info this is different since variables are accessible through out.
Would it be somehow possible (stop me if I'm asking too much here ) to configure which variables are accessible where? So on that basis it could save some system resources when you are not in the plugin, because the plugin has to monitor less? Not sure if that at all works like that (I think it should). Inside the plugin all variables can then be made accessible, on a global scale users can limit it?

Keep saying it, but also can't say it enough again!

Hi Joz,
currently a user had different options, to reduce CPU and memory usage.
All this options are bundled in the configuration dialog "Monitoring", most time/resource consuming functionalities (e.g. TV Server-, TV Client-Monitoring) or display options (e.g. Use of Gauges) can be switched on/off depending on performance capabilities of HTPCs. If a user does not use this plugin frequently (and does not include HTPCInfo properties in other skin files), there is also the chance to switch off the option "Load properties on startup". This means, that only a minimum of resources are allocated before the main window of HTPCInfo opens.
The last point, if it is possible to configure which properties are accessible where, needs a code re-design and many many new options. This is confusing for a user and because of this not in scope, sorry.
On my machine (2.2 GHz, 2 GByte RAM) all options are switched on and I have no performance problems. But I don't know, if this plugin works on older machines smoothly.

Cheers, Micropolis ;-)

 

[joz]

I got your points there Micropolis.

I was suggesting this because I do not have performance issues but HTPCInfo is kicking my machine up to higher power levels (P-states, Cool & Quiet paramater).
I managed to get it to settle on half throttling with RMClock (Multiplier of 9x = 1,8GHz) when idling MP. If I turn HTPCInfo off then it manages to stick with the lowest P-state (5x = 1 GHz). I'll experiment with the options in config, maybe disable the tv/client monitor since you suggest that being the most resource intensive.

Currently I have everything turned on and I can see spikes (which is actually quite good for now to test the stability of my undervolt ) in the throttling that's done. It gets up to high power for a second (or less) and then returns to either low or mid state. This happens on say a minute cycle. But as I said I'll test with settings and see what I can do to lower it all.
This issue occurs on my server/HTPC (which is the tv server also) and is on most of the time so I'd like to keep power usage to a minimum. My clients do not seem bothered by it at all but they are way more powerfull then the server is.


-------EDIT------

Disabled monitor tv clients and tv server on the machine but that did not really help. Also tried not loading the values on startup and then not go in the plugin and check the p-state, same deal, stuck @ 9x or higher (13) instead of between 5x and 9x
I think load will be important for the more energy aware MP users (like me). I will test a little more with these settings to see if I can get it to lower.

-------EDIT2------

I disabled also sensor monitoring and harddisk monitoring and when I run MP it still gets kicked up to 9x. It then is pretty stable on 9x, doesn't go up to 13x.
The weird thing is that I told RMClock to only throttle up when a load on one core reaches 80% of the maximum. However MP in taskmanager only takes up somewhere between 20 and 25 percent. 25% (with HTPCInfo on, little lower if off but isn't that big of a difference) of 1,8 GHz is 0,425 GHz (I know you can't really calculate like that but just for the sake of things for now), which is well below 80% of 1GHz.
So not really sure how all it is done but could it maybe be that you have some background workers doing work for you and maybe have set them on high or medium prio? And that's what's causing RMClock to throttle up unnecessarily? Maybe, if possible, a lowest priority for this is best?
It's not another process that's causing it, everything else takes up say 1 percent or something. RMClock does throttle down correctly when MP is off and when MP is on without HTPCInfo on.

 

[Micropolis]

HTPCInfo for MediaPortal v0.7.0

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:

• 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.

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

 

[m6242]

I installed your latest version. In Blue3wide i cant activate the details. Any advice why?

Still good Work. Go on with it

 

[Micropolis]

Hi m6242,
sorry, but what means "can't activate"? Is there no possibilty to open the window or is the window content only empty?
I hope, after I know this, it's easier to help you.

Cheers, Micropolis ;-)

 

[m6242]

Sorry what i want to say is, that i see the mainpage. If i make a click on the button "Detailansicht" the screen fade back ánd i am still at the "Main" HTPCinfo Screen.
I hope now you know what i want to say.

There was no error message while installing the mpe File.

 

[Micropolis]

HTPCInfo plugin for MediaPortal v0.7.0

Hi m6242,
after some (virtual) installations I must say, I cannot locate your specifc problem.
Currently, I'm assuming that you use the generic skin or an adapted version of included skin files. Please remember, that all 4 xml-files (HTPCInfo.xml, HTPCInfoOverview.xml, HTPCInfoDetails.xml and HTPCInfoGauges.xml) must be located in your skin folder. If not, the switching between screens cannot works. So please check this.
If this also not helps, you can open the configuration dialog and change (temporarily) the start screen. If you see now again some problems, send me a private message or try to deinstall/reinstall the plugin.

Cheers, Micropolis ;-)