Refresh guide task taking several hours

[stettler 30]

Hello,

Is it normal that the refresh task is taking several hours to update guide data from ServerWMC? On my setup, it's taking about 3 hours (it stays at 0% for a very long time) to get 14 days of datat for about 50 channels from a computer running ServerWMC on the same local net. Software like Remote Potato update the same data in a few seconds max, which seems logical as it's only a few KB of text. Or am I missing something? Is there a way to speed-up the task? (Emby clients are very unresponsive when accessing a server runing such a task)

 

Cheers!

 

 

[Luke 42085]

No, that's an unusually long time.

[stettler 30]

Ok! Here is a log of the refresh guide. There was no other task running at that time. (I changed the IP/address of the server)

http://www.cohprog.com/emby-refresh-guide-log.zip

 

I don't see anything that "obviously" takes time in the log. It seems to be generaly slow and process only a few data per minutes.

 

Emby server is running on a Windows 2012R2 server. There is plenty of free ram (10GB+) and the CPU is used at less than 50% (It's a Xeon E5 with 6 cores)

Edited August 19, 2016 by stettler

[stettler 30]

The ServerWMC log doesn't have anything special either. There just seems to be a "long" time (1-3 minutes) between individual requests:

 

2016/08/21 10:02:22.001 Received client request: MediaBrowser^@REGULUS@|2002:0:1:1::77|GetEntries|44054|1471762941|1472972541
2016/08/21 10:02:22.103 GetEntries> Channel: France 2 HD/3, EPG entries: 448
2016/08/21 10:02:22.104 Finished request GetEntries in 0.11s
2016/08/21 10:05:18.070 Received client request: MediaBrowser^@REGULUS@|2002:0:1:1::77|GetEntries|44222|1471763118|1472972718
2016/08/21 10:05:18.168 GetEntries> Channel: France 3/4, EPG entries: 557
2016/08/21 10:05:18.168 Finished request GetEntries in 0.10s
2016/08/21 10:08:11.874 MaintenanceTimer> Callback started...
2016/08/21 10:08:11.875 MaintenanceTimer> Callback completed in 0.00 sec.
2016/08/21 10:10:35.340 Received client request: MediaBrowser^@REGULUS@|2002:0:1:1::77|GetEntries|44224|1471763435|1472973035
2016/08/21 10:10:35.438 GetEntries> Channel: France 5/5, EPG entries: 382
2016/08/21 10:10:35.438 Finished request GetEntries in 0.10s
2016/08/21 10:12:56.141 Received client request: MediaBrowser^@REGULUS@|2002:0:1:1::77|GetEntries|44055|1471763576|1472973176
2016/08/21 10:12:56.244 GetEntries> Channel: M6 Suisse HD/6, EPG entries: 394
2016/08/21 10:12:56.244 Finished request GetEntries in 0.11s
2016/08/21 10:15:07.995 Received client request: MediaBrowser^@REGULUS@|2002:0:1:1::77|GetEntries|42470|1471763707|1472973307

 

Any idee what may be causing that or how to fix it?

Also, is there a technical reason to do individual request for each entires instead of downloading everything over a single request?

Edited August 21, 2016 by stettler

[stettler 30]

Sorry to bump this but is there anyway to get more debuging info about what is happening? Refreshing the guide data through ServerWMC is taking 3h for 100 channels or so (7 days of data). In the log, there seems to be several minutes between each data request which explain why  it's taking soo long.

 

Also, while the Guide refresh task is  running, other tasks are blocked (stay at 0%) and access to the whole Emby server, whatever from the web interface or from one of the various app, is very slow.

[stettler 30]

Uninstalling fully Emby Server and re-installing it fixed it (now taking a few minutes instead of 3h). I would have loved an easier method...