uploading image increases it's size
Hi
i've run into an issue where if i upload an image from a test case it is properly transformed and optimised, but on our production servers the size of file received from Cloudinary is significantly larger than supplied file.
sdk: java cloudinary-1.0.14
source code:
Transformation transformation =
new Transformation().effect("unsharp_mask:100").fetchFormat("jpg").quality(100).height(height).width(width);
imageOptions.put("transformation", transformation);
imageOptions.put("public_id", "new_random_id");
Map result = cloudinaryClient().uploader().upload(imageUrl, imageOptions);
This converts a file of ~6MB to ~2MB on a test system, but returns file of ~10MB on production servers with exact same source.
i am certain this is a minute detail and am also sure we are not running 2 different optimisations.
would be great to have some pointers on this.
-
to add to this, i've definitely tried out quality(auto:best) and that does compress the image, however i'd be of great help to understand why does quality(100) bloat the image in one case but not the other.
0 -
Hi,
I see that you contacted us directly via Zendesk where we've been discussing this in more details. In short, q_100 does increase the filesize in both cases, Test and Production, as the image stored in Cloudinary is the same in both uploads (and therefore the same ETag is generated based on image bytes). The difference would be in processing post-upload and how the image is requested/retrieved from Cloudinary for your Test and Production systems before they're uploaded to the converted/backup URLs that you shared with us.
0
Post is closed for comments.
Comments
2 comments