Closed Croq360 closed 3 years ago
Can you elaborate where the slowness happens? Processing in locast2tuner or in Plex/Emby?
On Mon, Apr 5, 2021 at 12:06 PM Croq360 @.***> wrote:
I've noticed that the program guide information that processes during initially running Locast2Tuner runs quite a bit slower (2x to 3x slower) than when I run Locast2Dvr.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/wouterdebie/locast2tuner/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABKABXVNL4DE3GHK6RAMM3THHUXLANCNFSM42ND5FZQ .
Processing in locast2tuner, right after it does the facilities info.
It takes 9 seconds to load my Phoenix channels in locast2tuner, but only about 2 seconds in locast2dvr.
I see there is somewhat of a difference, but I'm not seeing the 9 vs 2 secs:
Without remap:
2021-04-05T12:33:48 [INFO] - Loading stations for Phoenix (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:50 [INFO] - Loading stations for New York (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:52 [INFO] - Loading stations for Madison (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:54 [INFO] - Loading stations for Denver (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:57 [INFO] - Loading stations for Los Angeles (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:57 [INFO] - Starting http server for Multiplexer on http://127.0.0.1:6077
With remap:
2021-04-05T12:32:57 [INFO] - Loading stations for Phoenix (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:00 [INFO] - Loading stations for New York (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:02 [INFO] - Loading stations for Madison (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:04 [INFO] - Loading stations for Denver (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:07 [INFO] - Loading stations for Los Angeles (cache: true, cache timeout: 3600, days: 8)..
2021-04-05T12:33:07 [WARN] - Channels will be remapped!
2021-04-05T12:33:07 [INFO] - Starting http server for Multiplexer on http://127.0.0.1:6077
That said, I should probably move to the async client for loading as well
As long as it doesn't interfere with my recordings, I don't really have a problem with it, just something I noticed.
Is this still that case? I've moved to the async client and I'm wondering if this is still true.
I'll check my logs from my earlier restart of my service and let you know.
Update: it appears to be more comparable to what I was seeing with locast2dvr.
@Croq360 Thanks! I'm closing this issue for now, but don't hesitate to reopen if things get slow.
I've noticed that the program guide information that processes during initially running Locast2Tuner runs quite a bit slower (2x to 3x slower) than when I run Locast2Dvr.