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

Important usage of processors #11

Closed
iaeiou opened this issue Aug 30, 2021 · 5 comments
Closed

Important usage of processors #11

iaeiou opened this issue Aug 30, 2021 · 5 comments
Labels
question Further information is requested

Comments

@iaeiou
Copy link

iaeiou commented Aug 30, 2021

Bug description

I installed Yoga from Flatpak, then run a little test with 3 pictures, 6MB in total

What happened

A lot of resources are used by Yoga:

Capture d’écran de 2021-08-30 03-37-23

After a few minutes, I had to kill the process

What was expected

Optimize the pictures and keep the computer usable ;)

System information

  • Operating system (with version): Debian 10

  • How did you installed the software?

https://flathub.org/apps/details/org.flozz.yoga-image-optimizer

  • YOGA Image Optimizer version:

Version 1.0.0

Additional infos

I'm not familiar with Flatpak, is there a way to get relevant logs to report here?

@iaeiou iaeiou added the bug Something isn't working label Aug 30, 2021
@flozz
Copy link
Owner

flozz commented Aug 30, 2021

Hello,

It is not a bug: this level of optimization is a very heavy process (especially for JPEGs as Guetzli is really resources greedy). For your information, JPEG optimization takes, depending on the input image:

  • 1 to 5 minute per megapixel
  • 200 to 400 MB per megapixel

PNG optimization is lighter. More information here (it is in French, but Google Translate should help):

So YOGA may not be adapted to everyone needs. Personally, I use it on "not-so-big" pictures, and generally I start an optimization batch while I do not need the PC...

The next version, that will be released soon, will improve things a little bit:

  • The "Stop" button will effectively stop background threads (no more need to kill them manually),
  • The number of threads used for the optimization will be configurable (so it will be possible to use only one thread to continue using the PC at the same time).

:)

@flozz flozz added question Further information is requested and removed bug Something isn't working labels Aug 30, 2021
@iaeiou
Copy link
Author

iaeiou commented Aug 30, 2021

It is not a bug: this level of optimization is a very heavy process

Alright, I didn't know that, thank you!

PNG optimization is lighter. More information here (it is in French, but Google Translate should help):

No problem, I'm a native french speaker!

BTW, I discovered imgp (and plugged it with Vscode) today. imgp is "a command line image resizer and rotator for JPEG and PNG images", maybe some interesting bits for Yoga out there?

The next version, that will be released soon, will improve things a little bit:

Nice! Thanks for sharing this project,
cheers

@iaeiou iaeiou closed this as completed Aug 30, 2021
@flozz
Copy link
Owner

flozz commented Aug 30, 2021

BTW, I discovered imgp (and plugged it with Vscode) today. imgp is "a command line image resizer and rotator for JPEG and PNG images", maybe some interesting bits for Yoga out there?

YOGA will not handle image rotation (it is out of its scope), but the image resize is already available on the CLI, and will be available on the GUI in the next version (YOGA Image Optimizer v1.1.0) :)

@licaon-kter
Copy link

licaon-kter commented Sep 20, 2021

On Windows 1.1.0 doesn't seem to use that Setting correctly the whole time

Eg. For each file a thread is created on "Optimize" start, not when it actually processes the actual file. Making the machine behave oddly under the load, since if you have 1000 files to optimize it will create 1000 threads each using memory and resources, and each using 100% of one core for setting up. The system will starve at one point making even input erroneous (trying to write letters will input ljk!@@21';s/.//, so the letters and random punctuation signs). After the threads are created THEN it will start to use only X CPU threads as setup, if the machine still works that is :(

/LE: reworded for clarity

@flozz
Copy link
Owner

flozz commented Sep 23, 2021

@licaon-kter I moved your message in a new issue as it is probably not linked to this one ;)

#13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants