Search results

@moozooh I did. They just don't like the idea. Microservice is basically you buy a single or few VM or container to spawn separate server that only do a certain task. It won't take origin server's resource in any significant matter. This is one example how you can set up a image processing...

@moozooh High performing image processing library usually takes around 100ms to transform one fat image. Shared CPU and 128mb RAM VM Size even can transform a whole chapter within seconds. It's viable to set up image processing microservices below $10/month budget.

@Holo Bunny CDN overs a volume plan CDN with lesser pricing than most, but with less point of presence. You can outsource some of your traffic to that.

For anyone who thinks serve webp is complex, let me give this example. This is from my image proxy I implemented with Imaginary and Cloudflare workers. It grabs images with Mangadex API, convert it to requested format, then cached at Cloudflare CDN. WEBP version...

@Lymus Is outsourcing to multiple cloud providers really not an option? You know, there are some more efficient solutions for performance problems besides upgrading server every time you hit the wall. Some of them can be implemented without some significant code changes to your backend and can...

@kevinmul 1. No, converting image on the fly is actually one of web performance best practices that being encourage by performance experts (I learned about it from reading an article from a Google Engineer). Some image CDN services do this and cached images on CDN level, but for self-hosted...

@CatWEax I don't actually use those to store images from Mangadex. Imaginary does optimize and resize images from Mangadex, but by default it's doing it on the fly. I'm using Cloudflare Workers to cache the result so it doesn't convert to WEBP twice if I get the same image later.

@Lymus There's no reason not to use WEBP because some browsers don't support it. There are ways to serve WEBP images with fallbacks to either JPG or PNG. One of them is using <picture></picture> tags to wrap two different image types with WEBP as the main image and the other way is to check...

Is mozJPEG can really make text unreadable? Forgive for my ignorance, but I never heard rescale has that kind of unintended side effect--unless it forcefully resized from low-res to high-res, that I'm aware. And I don't know why you want to compress images on delivery, you at least need to set...

Have you guys consider optimizing images with mozJPEG or WEBP upon upload? I tested optimizing a random image from one manga, and without sacrificing noticable quality it can be smaller up to 2x-3x than the original...