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
MediaPortal 1 Plugins
[Plugin] MPSync - MediaPortal multi-seat Synchronization
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="m3rcury" data-source="post: 992825" data-attributes="member: 106370"><p>lulsam, thanks for the feedback. I did some tuning in the latter version and in the next one, it will be even faster! I introduced triggers to indicate which tables in the databases have changed. This avoids scanning all tables on both source and target and comparing the record contents. It will be less taxing on the HTPC CPU usage and IO.</p><p> </p><p>I will still allow the 1.0.0.5 synchronization method for those who do not want to have triggers created in the databases, but with the triggers, it is a hell lot faster!</p><p> </p><p>I have also introduced database integrity checking on plugin startup, hence it will take a couple of minutes (depending on database size) to start the synchronization, but this should fix corrupted target databases and avoid plugin to stall.</p><p> </p><p>Regards</p></blockquote><p></p>
[QUOTE="m3rcury, post: 992825, member: 106370"] lulsam, thanks for the feedback. I did some tuning in the latter version and in the next one, it will be even faster! I introduced triggers to indicate which tables in the databases have changed. This avoids scanning all tables on both source and target and comparing the record contents. It will be less taxing on the HTPC CPU usage and IO. I will still allow the 1.0.0.5 synchronization method for those who do not want to have triggers created in the databases, but with the triggers, it is a hell lot faster! I have also introduced database integrity checking on plugin startup, hence it will take a couple of minutes (depending on database size) to start the synchronization, but this should fix corrupted target databases and avoid plugin to stall. Regards [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
[Plugin] MPSync - MediaPortal multi-seat Synchronization
Contact us
RSS
Top
Bottom
