That's excellent! Very nice automation. I imagine that our workload for images is not large at the moment. If the CPU is being scheduled to scan storage at a lower priority than for realtime membership activity, I guess we'll learn at what point does image processing can't be serviced in a timely manner.
Based on what I've been seeing, that won't be a problem. Lemmy isn't very heavy on the CPU, and the image processing spikes the CPU for a second or two every 5 minutes.
Well, I love that we don't have to resort to Imgur which drives me nuts most of the time.
Oh, that's really interesting! Does our hosting server have a GPU?
I thought I needed a GPU, but it turns out that's only if you want it to scan things before it ever makes it to storage. It can detect using CPU but it's not fast enough to catch things during upload. Instead it scans for new things every 10 seconds or so.
@walden @[email protected] Ah, that's good to know! Noice!
Well, no matter what I try I can't get it to work on the server. It works in my homelab which has direct access to some CPU cores but no GPU (not even intel graphics), but when I run it on the host server it spikes the CPU to 100%, crashes, and starts the cycle over again.
I'll keep it running locally for now, as it's a pretty small service overall.
This community is for official announcements from the administrators of sub.wetshaving.social.