asonix
I've put all the demo code in a repo on my forgejo: https://git.asonix.dog/asonix/flume-deadlock
Cool, the PKGBUILD has been updated
The logs presented are not related to the problem, and are actually not important. Sled doesn't like when you constrain it's RAM but it won't cause issues. Cleaning up ImageMagick's...
that does point to an issue in pict-rs for cleaning up tmp files when imagemagick, ffmpeg, or exiftool get killed. I'll look into this for 0.4 stable
oh, just re-read your command for cleaning the orphaned files. those `magick-` files are left behind by imagemagick, and i'm hesitant to add logic to pict-rs to clean them in...
alternatively, you could play with the values in imagemagick's policy xml file. This is the default one pict-rs ships with: https://git.asonix.dog/asonix/pict-rs/src/branch/main/docker/object-storage/root/usr/lib/ImageMagick-7.1.0/config-Q16HDRI/policy.xml it needs to be mounted to `/usr/lib/ImageMagick-7.1.0/config-Q16HDRI/policy.xml` inside the...
in my testing locally, I've gotten the backgrounded upload path (with minio object-storage) down to 300ms when uploading two files in the same request, one around 30MB and one around...
i'm not saying the processing time is 300ms, i'm saying the _upload_ time for 45MB is 300ms in my local testing. The processing time is longer, especially for videos where...
if you think about how these paths work: an upload is reading bytes and saving them to storage processing an image or video is reading bytes, decoding the bytes, possibly...
Additionally, I've already implemented support for backgrounded uploads in both my `pict-rs-proxy` and `pict-rs-aggregator` example projects. - pict-rs-proxy offloads queuing retries to the client, refreshing a page from javascript every...