Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image weight optimization #33

Open
fbunoz opened this issue Jan 6, 2017 · 1 comment
Open

Image weight optimization #33

fbunoz opened this issue Jan 6, 2017 · 1 comment

Comments

@fbunoz
Copy link

fbunoz commented Jan 6, 2017

I uploaded a photo : 912 x 1216 px and 528 518 bytes.
The most of my images have this size (or 1216 x 912 px), because it correspond to 1/3 of the full size of my APN. I prefer reduce the size with an integer ratio to optimize the noise reduction.
I reduce the size to ~1200px and 4-500ko to limit the weigth of the images on the c2c server. I use a bigger size (weigth : ~1Mo) only for very beautiful photos or reusable photos to add route track.

But the result is :

It means that the original photo has been resized (without change the size) to generate the BI photo, although it was not necessary. And the resizing has increased the weight !
On the V5, when the original size was smaller than BI max size, the photo was not resized for BI, and on the disk a simple unix link was created to the original photo. The disk space was saved.
On the V6, we lost 535 kB.

If we can't use unix link for BI, it would better to generate a BI image lighter than the original.

@arnaud-morvan
Copy link
Member

Note that we cannot use unix links anymore as we use S3 storage.
IMHO, creating the BI image by resizing to the same size from 528 Ko to 547 Ko is insignificant.

lbesson pushed a commit that referenced this issue Jan 14, 2021
[requires.io] dependency update on master branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants