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
Improvement Suggestions
5111: Parallel DVB EPG
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="CyberSimian" data-source="post: 1275042" data-attributes="member: 141969"><p><strong>Testing methodology</strong></p><p>(1) I have attempted to run the test cases under identical conditions, but as each run takes around 30 minutes, it was not possible to run the test cases more than once (the HTPC was required for other purposes). Running each test case multiple times would be useful, as it would indicate how consistent the results are.</p><p></p><p>(2) I have included the log files in the attached zip, but I took the liberty of using my <strong>logclean.rex</strong> script to delete all of the power-scheduler lines, as those lines create noise in the log file (but I have retained the original log files if you need them). I have included the screen shots in the zip file too.</p><p></p><p>(3) I also wrote an <strong>epgstats.rex</strong> script to scan a log file and produce some summary statistics for it, to make it easier to compare the different test cases. I have included these statistics files (file extension TXT) in the zip file.</p><p></p><p>(4) To compare the test cases, the following criteria can be used:</p><ul> <li data-xf-list-type="ul">The duration of the grabbing phase</li> <li data-xf-list-type="ul">The duration of the database-update phase</li> <li data-xf-list-type="ul">The number of channels updated in the database</li> <li data-xf-list-type="ul">The number of programmes updated in the database</li> <li data-xf-list-type="ul">The total duration (grabbing + DB update + other)</li> </ul><p>When a single grabber is used, the total duration is only slightly more than the sum of the grabbing phase and the database-update phase. But this does not apply when multiple grabbers are used, as the grabbers run in parallel (so for multiple grabbers, the sum of the individual parts <em>exceeds</em> the total duration).</p><p></p><p></p><p><strong>Test cases</strong></p><p>(1) Old DLLs, timeshift grabber, 1 channel selected, using these settings:</p><p></p><p>[ATTACH]206083[/ATTACH] [ATTACH]206084[/ATTACH] [ATTACH]206085[/ATTACH]</p><p></p><p>These are the settings that I use on my production system (but this test was performed on my test system). The channel selected can be any 24-hour channel, but in my case it happens to be a radio channel. Note that screen shot 1 shows the settings for test (3) below (new DLLs); test (1) did indeed use the old DLLs.</p><p></p><p>(2) Old DLLs, idle grabber, 1 channel selected (settings same as (1)).</p><p></p><p>(3) New DLLs, idle grabber, 1 channel selected (settings same as (1)).</p><p></p><p>(4) New DLLs, idle grabber, 6 channels selected, using these settings:</p><p></p><p>[ATTACH]206086[/ATTACH] [ATTACH]206087[/ATTACH] [ATTACH]206088[/ATTACH] [ATTACH]206089[/ATTACH]</p><p></p><p>There are 9 MUXes that serve my location in the UK, but 3 of them are too weak to receive reliably, so I have deleted those from the "tuning details" file, leaving me with 6 MUXes. Since I have 6 tuners, I selected one channel in each MUX so that each tuner could tune to a different MUX. The other settings are set appropriately for this. The screen shot shows only 4 channels selected; the other two are later in the list (off screen).</p><p></p><p>(5) New DLLs, timeshift grabber, 1 channel selected (settings same as (1)).</p><p></p><p></p><p><strong>Summary of results</strong></p><p>[code] Grab DB Update Total Channels Programs</p><p>Test Case Duration Duration Duration Updated Updated</p><p>--------------------- -------- --------- -------- -------- --------</p><p>old, t/shft, 1 chan 6m 33s 19m 35s 26m 8s 141 25825</p><p>old, idle, 1 chan 8m 26s 19m 10s 27m 37s 141 25746</p><p>new, idle, 1 chan 18m 56s 19m 28s 38m 27s 141 25828</p><p>new, idle, 6 chans 15m 10s 3m - 7m 22m 12s 123 22420</p><p>new, t/shft, 1 chan 18m 27s 19m 3s 37m 31s 141 25852</p><p>--------------------- -------- --------- -------- -------- --------[/code]</p><p></p><p></p><p></p><p><strong>Observations</strong></p><p>(1) When a single grabber is used, the duration of the database-update phase is re-assuringly consistent, at around 19-20 mins on my system. No conclusions can be drawn from the database update time for multiple grabbers, since each grabber updates only a single MUX (instead of a single grabber updating all MUXes).</p><p></p><p>(2) When a single grabber is used, the number of channels updated in the database is always the same (141). When multiple grabbers are used, this value drops to 123. It is not apparent why this value is smaller.</p><p></p><p>(3) The number of programmes updated in the database is likely to vary slightly throughout the day. The UK EPG has 7 full days of EPG plus the remainder of the current day. It is probable that as each programme finishes broadcasting, its EPG entry is removed from the broadcast EPG carousel (to minimise datastream). As a result, the EPG received will shrink slightly thoughout the day, until midnight arrives when 24-hours of new EPG is added. </p><p></p><p>The tests do show a small variation in the number of programmes updated in the database, although the number does not always get smaller as might be expected.</p><p></p><p>However, the multiple-grabbers case shows a value that is around 3400 programmes smaller. Again, it is not apparent why this might be the case.</p><p></p><p>(4) When multiple grabbers are used, the duration of grabbing is very similar for each MUX (at around 15 minutes). </p><p></p><p>What is more concerning is that for the one-grabber case, the duration of grabbing is considerably longer when using the new DLLs compared to the old DLLs. For the one-grabber case, grabbing takes around 6-8 mins for the old DLLs, but takes 18-19 mins for the new DLLs. It is not apparent why this might be.</p><p></p><p>(5) Despite the unexpectedly large grabbing duration for the multiple grabbers case, this case in fact has the smallest total duration <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />. On the other hand, it seems to have missed 18 channels and around 3400 programmes. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /></p><p></p><p></p><p><strong>Desiderata</strong></p><p>One test that I have not run is the test that corresponds exactly to the settings shown in <a href="https://forum.team-mediaportal.com/threads/some-problems-with-dvb-epg.139717/post-1274234" target="_blank">post 35</a>. I wll try this if it will provide some useful results, but I am not sure that it is appropriate for the UK. As far as I can see from the screen shots, every channel is selected. In my EPG in MP, I have 73 TV channels and 32 radio channels. If every one of those were selected, I have a suspicion that the grabbing would run for hours <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite9" alt=":eek:" title="Eek! :eek:" loading="lazy" data-shortname=":eek:" /> (because TV server would tune to each of the 105 channels in turn, taking 15 minutes to grab each channel, but using 6 tuners, and so taking 105*15/6 = 262 mins, i.e. over 4 hours <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite9" alt=":eek:" title="Eek! :eek:" loading="lazy" data-shortname=":eek:" />).</p><p></p><p>Let me know if you want me to try different combinations of settings or repeat some of the tests to see how consistent they are. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1275042, member: 141969"] [b]Testing methodology[/b] (1) I have attempted to run the test cases under identical conditions, but as each run takes around 30 minutes, it was not possible to run the test cases more than once (the HTPC was required for other purposes). Running each test case multiple times would be useful, as it would indicate how consistent the results are. (2) I have included the log files in the attached zip, but I took the liberty of using my [b]logclean.rex[/b] script to delete all of the power-scheduler lines, as those lines create noise in the log file (but I have retained the original log files if you need them). I have included the screen shots in the zip file too. (3) I also wrote an [b]epgstats.rex[/b] script to scan a log file and produce some summary statistics for it, to make it easier to compare the different test cases. I have included these statistics files (file extension TXT) in the zip file. (4) To compare the test cases, the following criteria can be used: [LIST] [*]The duration of the grabbing phase [*]The duration of the database-update phase [*]The number of channels updated in the database [*]The number of programmes updated in the database [*]The total duration (grabbing + DB update + other) [/LIST] When a single grabber is used, the total duration is only slightly more than the sum of the grabbing phase and the database-update phase. But this does not apply when multiple grabbers are used, as the grabbers run in parallel (so for multiple grabbers, the sum of the individual parts [i]exceeds[/i] the total duration). [b]Test cases[/b] (1) Old DLLs, timeshift grabber, 1 channel selected, using these settings: [ATTACH]206083[/ATTACH] [ATTACH]206084[/ATTACH] [ATTACH]206085[/ATTACH] These are the settings that I use on my production system (but this test was performed on my test system). The channel selected can be any 24-hour channel, but in my case it happens to be a radio channel. Note that screen shot 1 shows the settings for test (3) below (new DLLs); test (1) did indeed use the old DLLs. (2) Old DLLs, idle grabber, 1 channel selected (settings same as (1)). (3) New DLLs, idle grabber, 1 channel selected (settings same as (1)). (4) New DLLs, idle grabber, 6 channels selected, using these settings: [ATTACH]206086[/ATTACH] [ATTACH]206087[/ATTACH] [ATTACH]206088[/ATTACH] [ATTACH]206089[/ATTACH] There are 9 MUXes that serve my location in the UK, but 3 of them are too weak to receive reliably, so I have deleted those from the "tuning details" file, leaving me with 6 MUXes. Since I have 6 tuners, I selected one channel in each MUX so that each tuner could tune to a different MUX. The other settings are set appropriately for this. The screen shot shows only 4 channels selected; the other two are later in the list (off screen). (5) New DLLs, timeshift grabber, 1 channel selected (settings same as (1)). [b]Summary of results[/b] [code] Grab DB Update Total Channels Programs Test Case Duration Duration Duration Updated Updated --------------------- -------- --------- -------- -------- -------- old, t/shft, 1 chan 6m 33s 19m 35s 26m 8s 141 25825 old, idle, 1 chan 8m 26s 19m 10s 27m 37s 141 25746 new, idle, 1 chan 18m 56s 19m 28s 38m 27s 141 25828 new, idle, 6 chans 15m 10s 3m - 7m 22m 12s 123 22420 new, t/shft, 1 chan 18m 27s 19m 3s 37m 31s 141 25852 --------------------- -------- --------- -------- -------- --------[/code] [b]Observations[/b] (1) When a single grabber is used, the duration of the database-update phase is re-assuringly consistent, at around 19-20 mins on my system. No conclusions can be drawn from the database update time for multiple grabbers, since each grabber updates only a single MUX (instead of a single grabber updating all MUXes). (2) When a single grabber is used, the number of channels updated in the database is always the same (141). When multiple grabbers are used, this value drops to 123. It is not apparent why this value is smaller. (3) The number of programmes updated in the database is likely to vary slightly throughout the day. The UK EPG has 7 full days of EPG plus the remainder of the current day. It is probable that as each programme finishes broadcasting, its EPG entry is removed from the broadcast EPG carousel (to minimise datastream). As a result, the EPG received will shrink slightly thoughout the day, until midnight arrives when 24-hours of new EPG is added. The tests do show a small variation in the number of programmes updated in the database, although the number does not always get smaller as might be expected. However, the multiple-grabbers case shows a value that is around 3400 programmes smaller. Again, it is not apparent why this might be the case. (4) When multiple grabbers are used, the duration of grabbing is very similar for each MUX (at around 15 minutes). What is more concerning is that for the one-grabber case, the duration of grabbing is considerably longer when using the new DLLs compared to the old DLLs. For the one-grabber case, grabbing takes around 6-8 mins for the old DLLs, but takes 18-19 mins for the new DLLs. It is not apparent why this might be. (5) Despite the unexpectedly large grabbing duration for the multiple grabbers case, this case in fact has the smallest total duration :). On the other hand, it seems to have missed 18 channels and around 3400 programmes. :( [b]Desiderata[/b] One test that I have not run is the test that corresponds exactly to the settings shown in [URL='https://forum.team-mediaportal.com/threads/some-problems-with-dvb-epg.139717/post-1274234']post 35[/URL]. I wll try this if it will provide some useful results, but I am not sure that it is appropriate for the UK. As far as I can see from the screen shots, every channel is selected. In my EPG in MP, I have 73 TV channels and 32 radio channels. If every one of those were selected, I have a suspicion that the grabbing would run for hours :eek: (because TV server would tune to each of the 105 channels in turn, taking 15 minutes to grab each channel, but using 6 tuners, and so taking 105*15/6 = 262 mins, i.e. over 4 hours :eek:). Let me know if you want me to try different combinations of settings or repeat some of the tests to see how consistent they are. :) -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
5111: Parallel DVB EPG
Contact us
RSS
Top
Bottom