99% CPU Utilisation on Emby Server

[mrees 6]

Hi all,

 

I have for the first time installed Emby server and I'm currently trying to get the system up and running

I have asked the server to catalog my tv series to start off with as a test (quite a lot of data)

 

Currently all though there doesn't appear to be any cataloging occurring, and there are no clients attached the the server, the server is still running at 99% CPU utilization

 

Any ideas to what may be causing this?

It fluctuates between about 92 and 99% utilization

 

i did try searching the forums for some answers about places to look for troubleshooting

Apologies if I missed something, I'm still trying to get my head around everything

 

Thanks for your time

 

[ebr 16177]

Why do you say nothing is going on?

 

Do all of the scheduled tasks report that they aren't running?

 

Did your library scan complete successfully?

[mrees 6]

Wow, thanks so much for the quick response I really appreciate your help

 

The server is a new build. I have a few test clients setup to them, but they don't seem to be responding too well (spinning circle when navigating, no guarantee of playback if you can locate the episode etc)

 

The scheduled tasks show nothing too recent

I believe the library scan completed successfully, but Im not sure as I cant easily browse to library on the clients as they are not very responsive (possibly due to the high server utilization)

I can see a database clean cancelled below, the only reason that may have occurred could be due to a server bounce. I didn't deliberately cancel anything

 

[speechles 2055]

Is it perhaps populating missing people until these are built up? This is done on demand as apps request the server goes and gets the info at that time. It might just be your caches of images, as well as people and other incidentals which dont show as a scheduled task. If you refresh things, say an entire library this also wont cause a task to show but will impact your cpu.

 

Sent from my Nexus 7 using Tapatalk

[mrees 6]

Thanks so much for your reply

So should I just let it do its thing and check back in at a later point?

It is indexing a lot. There is about 13TB of TV series data alone and the internet link is a woeful 3-4MB/s

[speechles 2055]

The best advice I can offer you is, don't panic.

 

If your internet is that speed, it will take longer, as well as emby will throttle requests to keep within limits metadata providers have set. So it might take longer for things to fully populate. Some features (people) only populate when requested by an app. This is so scan times are reduced. So as you browse cast and crew these build-up when requested. If you browse into alot of these, the task which fetches these might lock up your entire image fetching ability until subsequent requests finish. So you would see horrible response times for images then suddenly it works instantly.

 

The honestly best thing you could do is let emby finish fully scanning your library. Wait until all apps are finished browsing. Close all clients using emby. now check after 15 minutes is the server still running at 90%? This now assumes no clients are making requests which could be causing it.

 

You also may also want to use the imdb people downloader by radeon to reduce load on your emby server to avoid these image waits that on-demand people loading creates.

 

http://emby.media/community/index.php?/blog/1/entry-35-imdb-ibn-people-downloader-v2/

 

Sent from my Nexus 7 using Tapatalk

Edited June 13, 2016 by speechles

[Luke 42078]

Hi, the best way to get an answer as to what was happening is by proving the emby server log from the time-frame of that activity. Instructions on how to do that are here:

 

http://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks.

[mrees 6]

Thanks again for everyones help. I really appreciate it

 

Log has been attached for latest effected time period

 

Cheerz

11.59-1306 Server Log.txt

[mrees 6]

The issue seems to have died down. Thanks for everyones 2cents and help

[ebr 16177]

I would also make sure that clean database task completes successfully.  It shows it was cancelled above.