• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Slow Loading/100% CPU For Thumbnails

     
    • 1 Vote(s) - 5 Average

    Slow Loading/100% CPU For Thumbnails

    SilvaNights
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2025 Aug
    Reputation: 0
    #1
    2025-08-04, 11:45 PM
    Version 10.10.7
    Linux Docker container with hardware acceleration + 8GB RAM
    Server using Intel N100
    Windows 11 clients - Chrome/Edge

    Hi,

    When clients look at the available movies or tv shows there is a delay in loading the thumbnails/cards (they are blurred), on the server side it spikes to 100% CPU until they load on the client.

    Not sure what is happening here on the server when this happens, is it generating or pulling them?
    All the normal scheduled tasks are enabled and the appropriate metadata pullers are active too.

    Is it possible to speed up this process, pre-generate anything beforehand or use the NVME as a cache for these thumbnails?
    The media files are on a file server using HDD's and the JellyFin container is on an NVME SSD.

    Thanks.
    RobinHood70
    Offline

    Junior Member

    Posts: 1
    Threads: 0
    Joined: 2025 Aug
    Reputation: 0
    #2
    2025-08-06, 12:55 PM
    I can confirm this behaviour from the client side in Jellyfin Media Player as well. I don't have ready access to the server.
    bitmap
    Offline

    Community Moderator

    Posts: 1,060
    Threads: 9
    Joined: 2023 Jul
    Reputation: 30
    #3
    2025-08-06, 03:15 PM
    Recreate the behavior and throw your Jellyfin logs up on a pastebin site like privatebin.net.
    Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage

    [Image: AIL4fc84QG6uSnTDEZiCCtosg7uAA8x9j1myFaFs...qL0Q=w2400]
    SilvaNights
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2025 Aug
    Reputation: 0
    #4
    Yesterday, 11:50 PM
    (2025-08-06, 03:15 PM)bitmap Wrote: Recreate the behavior and throw your Jellyfin logs up on a pastebin site like privatebin.net.

    Apologies for the delay, please see here:
    https://pastebin.com/a9bhcHRH

    I can see loads of these showing up in the debug logs when I have the issue.
    Let me know if you require the whole log.

    Thanks.
    hmfaysal
    Offline

    Junior Member

    Posts: 2
    Threads: 0
    Joined: 2025 Jul
    Reputation: 0
    Country:Bangladesh
    #5
    Today, 12:47 AM (This post was last modified: Today, 12:56 AM by hmfaysal. Edited 3 times in total.)
    I am having the same problem, for the time being solved it with aggressive nginx proxy caching

    Code:
        # Images / Thumbnails
        location ~ ^/Items/.*/Images/ {
            proxy_pass http://127.0.0.1:8096;

            proxy_http_version 1.1;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;

            # --- disk cache ---
            proxy_cache          jfimg;
            proxy_cache_valid    200 1y;          # honour upstream max-age if present
            proxy_cache_revalidate on;
            proxy_cache_lock    on;              # avoid stampedes
            proxy_cache_key      "$scheme$proxy_host$request_uri";
            add_header          X-Cache-Status $upstream_cache_status always;

            # --- browser cache ---
            expires 1y;
            add_header Cache-Control "public, immutable";

            # Small buffers are fine for images; leave buffering on for speed
            proxy_buffering      on;
            proxy_buffer_size    64k;
            proxy_buffers        8 64k;
            proxy_busy_buffers_size 256k;
        }

    I am well aware this is not a permanent solution. But this has to do for now till we get a better solution. Open to any suggestion
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode