Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 200377" data-attributes="member: 21313">I'm testing with your test-files as I type this <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp; So far, all is going OK, hope to reproduce your error though.As far as the speed is concerned, I notice that SQL Express eats up over 50% of the CPU time and the TvScheduler service is only using 3% CPU or so.&nbsp; I guess that's more or less normal since most of the work going on is querying/updating the database.A good tip would be to schedule a guide update to be done at night.&nbsp; I can try to see how I could optimize the importing, perhaps there are some possibilities there.&nbsp; But I did write it to be very &quot;friendly&quot;, meaning it looks in the database to see what's already (possiblly) there and acts accordingly, and I wouldn't want to take that out again.</blockquote>

[QUOTE="dvdfreak, post: 200377, member: 21313"] I'm testing with your test-files as I type this :) So far, all is going OK, hope to reproduce your error though. As far as the speed is concerned, I notice that SQL Express eats up over 50% of the CPU time and the TvScheduler service is only using 3% CPU or so. I guess that's more or less normal since most of the work going on is querying/updating the database. A good tip would be to schedule a guide update to be done at night. I can try to see how I could optimize the importing, perhaps there are some possibilities there. But I did write it to be very "friendly", meaning it looks in the database to see what's already (possiblly) there and acts accordingly, and I wouldn't want to take that out again. [/QUOTE]

Verification