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
Development
General Development (no feature request here!)
Yet a couple of other performance suggestions
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="ojo" data-source="post: 3407" data-attributes="member: 10402"><p>After the general idear having XML nodes cached into a HashTable and proving at least a factor 10 performance optimization, I would suggest rewriting XML.cs even futher. (See other post "profiling for performance")</p><p></p><p>Instead of just caching the XML file into a XMLDocument using a Singleton pattern, it would be better to cache the document into a Hashtable, thereby optimizing both object creation and access to entries. This could bedone since the MediaPortal.XML never exceeds 2 levels of xml-nodes (besided the root-node). Just cache the elements with the key as <<section>>\<<entry>>.</p><p></p><p>Having the MediaPortal.xml cached also means that the idear of FileWatcher looking for changes done from the configuration or by hand also must be implemented.</p><p></p><p>I expect this to cut down memory-usage and garbage collections during load quite considerable. It will also speed up performance during load, but "only" about further 4-5 percent.</p><p></p><p>Just to be speciffic. This will only reduce load time of MP, not overall performance running the app.</p><p></p><p>Ojo</p></blockquote><p></p>
[QUOTE="ojo, post: 3407, member: 10402"] After the general idear having XML nodes cached into a HashTable and proving at least a factor 10 performance optimization, I would suggest rewriting XML.cs even futher. (See other post "profiling for performance") Instead of just caching the XML file into a XMLDocument using a Singleton pattern, it would be better to cache the document into a Hashtable, thereby optimizing both object creation and access to entries. This could bedone since the MediaPortal.XML never exceeds 2 levels of xml-nodes (besided the root-node). Just cache the elements with the key as <<section>>\<<entry>>. Having the MediaPortal.xml cached also means that the idear of FileWatcher looking for changes done from the configuration or by hand also must be implemented. I expect this to cut down memory-usage and garbage collections during load quite considerable. It will also speed up performance during load, but "only" about further 4-5 percent. Just to be speciffic. This will only reduce load time of MP, not overall performance running the app. Ojo [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Yet a couple of other performance suggestions
Contact us
RSS
Top
Bottom