home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Speeding up Media Portal Boot
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Scythe42" data-source="post: 941544" data-attributes="member: 95833"><p>Plugins are the main problem. They can be loaded/started while MP already shows basic home. If you select a window, which uses a certain plugin the contents are only shown when the plugin is ready. Need to check it in detail where it has side effects. Initial tests have shown that it might work this way with current master.</p><p> </p><p>Probably some additional checks or a general "Loading XML" would help greatly (darken current window/element, overlay with a Loading Animation like the Wait Cursor or just the part where it is showing its contents) is needed if a plugin could cause problems. Need to test in detail. No change to Skins needed. MP should handle this.</p><p> </p><p>This can be done without changing the plugin architecture. Even though there is huge potential doing some overhaul here in the way MP handles them.</p><p> </p><p>But on my current test builds with MP out of the Box and the following Plugins:</p><ul> <li data-xf-list-type="ul">Fanart Handler</li> <li data-xf-list-type="ul">Latest Media Handler</li> <li data-xf-list-type="ul">Moving Pictures</li> <li data-xf-list-type="ul">TV Series</li> <li data-xf-list-type="ul">My Films</li> <li data-xf-list-type="ul">Online Videos</li> <li data-xf-list-type="ul">Power Scheduler++</li> <li data-xf-list-type="ul">Sub Central</li> <li data-xf-list-type="ul">Trakt</li> <li data-xf-list-type="ul">Info Service</li> <li data-xf-list-type="ul">IMDB+</li> <li data-xf-list-type="ul">Fritz Box Manager</li> <li data-xf-list-type="ul">Browse the web</li> <li data-xf-list-type="ul">Event Ghost Plus</li> <li data-xf-list-type="ul">Weather Thingy by Micropolis (forgot the exact Name)</li> </ul><p>I have a startup time of a few seconds on a four year old machine. A bit slower than XBMC though. Splash-Screen stays active in the background for a couple of seconds still show initialising stuff while MP is already there (as it is not D3D, which the rest is). Tested with StreamedMP, Default/Default Wide and of course Titan.</p><p> </p><p>In addition the general delayed loading of some resources should be changed to background loading. This will make MP feel a bit snappier. This will happen with a replacement of the TextureManger/FontEngine.</p><p> </p><p>Also this stuff should stay in memory. We are talking 4MB compared to 16MB on DefaultWide for example. No need to conserve GPU memory here. We hardly use any and the skins are still small anyway. There is no noteworthy difference in startup time by loading all GFX stuff directly. But as said: delayed loading should be switched to background loading.</p><p> </p><p>Not loading/disposing stuff on demand helps a lot in general. It should make even TV Zapping a bit faster as well (there are some Load()/Dispose() involved if I am not mistaken). We have way too many plugins/windows defined as "delayed loading" anyway or freeing up there resources all the time and re-allocating them later.</p><p> </p><p>Also Input Devices seems to cause some problems. There are some checks involved depending on what you activated that cause additional delay until it runs in a timeout. Haven't figured out which ones yet.</p></blockquote><p></p>
[QUOTE="Scythe42, post: 941544, member: 95833"] Plugins are the main problem. They can be loaded/started while MP already shows basic home. If you select a window, which uses a certain plugin the contents are only shown when the plugin is ready. Need to check it in detail where it has side effects. Initial tests have shown that it might work this way with current master. Probably some additional checks or a general "Loading XML" would help greatly (darken current window/element, overlay with a Loading Animation like the Wait Cursor or just the part where it is showing its contents) is needed if a plugin could cause problems. Need to test in detail. No change to Skins needed. MP should handle this. This can be done without changing the plugin architecture. Even though there is huge potential doing some overhaul here in the way MP handles them. But on my current test builds with MP out of the Box and the following Plugins: [LIST] [*]Fanart Handler [*]Latest Media Handler [*]Moving Pictures [*]TV Series [*]My Films [*]Online Videos [*]Power Scheduler++ [*]Sub Central [*]Trakt [*]Info Service [*]IMDB+ [*]Fritz Box Manager [*]Browse the web [*]Event Ghost Plus [*]Weather Thingy by Micropolis (forgot the exact Name) [/LIST] I have a startup time of a few seconds on a four year old machine. A bit slower than XBMC though. Splash-Screen stays active in the background for a couple of seconds still show initialising stuff while MP is already there (as it is not D3D, which the rest is). Tested with StreamedMP, Default/Default Wide and of course Titan. In addition the general delayed loading of some resources should be changed to background loading. This will make MP feel a bit snappier. This will happen with a replacement of the TextureManger/FontEngine. Also this stuff should stay in memory. We are talking 4MB compared to 16MB on DefaultWide for example. No need to conserve GPU memory here. We hardly use any and the skins are still small anyway. There is no noteworthy difference in startup time by loading all GFX stuff directly. But as said: delayed loading should be switched to background loading. Not loading/disposing stuff on demand helps a lot in general. It should make even TV Zapping a bit faster as well (there are some Load()/Dispose() involved if I am not mistaken). We have way too many plugins/windows defined as "delayed loading" anyway or freeing up there resources all the time and re-allocating them later. Also Input Devices seems to cause some problems. There are some checks involved depending on what you activated that cause additional delay until it runs in a timeout. Haven't figured out which ones yet. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Speeding up Media Portal Boot
Contact us
RSS
Top
Bottom