Handle_path high cpu

Hello! So I’m running Caddy2 to reverse_proxy https://octoprint.org/ and GitHub - jacksonliam/mjpg-streamer: Fork of http://sourceforge.net/projects/mjpg-streamer/. Works great for octoprint, however whenever I use the /webcam path, cpu on spikes to 50%+ on one core.

*.example.com {
    tls {
        issuer zerossl {
            disable_http_challenge
            disable_tlsalpn_challenge
            resolvers 1.1.1.1 8.8.8.8
            dns cloudflare <key>
            }
        }
    reverse_proxy localhost:5000
    handle_path /webcam* {
        reverse_proxy localhost:8080
    }
}

While directly connecting to GitHub - jacksonliam/mjpg-streamer: Fork of http://sourceforge.net/projects/mjpg-streamer/, I see about 2-4% cpu usage on one core.

Note that I am running caddy v2 on a raspberry pi 4b 8gb, so perhaps arm64 is coming into play here? Either way, I’m surprised cpu spikes that much, though mjpeg does make a lot of requests. Do you think this is normal? Is there any optimizations to be had here in my config? Thanks!

This topic was automatically closed after 30 days. New replies are no longer allowed.