-
Notifications
You must be signed in to change notification settings - Fork 57
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
migrate graphicsmagick to Pillow #107
base: master
Are you sure you want to change the base?
Conversation
Happy to see interest in using of Pillow instead of using subprocesses and imagemagick.
in python3 is unnecessary since division of two int give a float by default (
Here is my python test script for benchmarking resizing of images (github is not letting me add .py files as attachments):
IIRC though, there isn't substantial improvement when using pillow single threaded because it uses only one core of the CPU, while imagemagick is using all of them when calling subprocess. The main reason why I stopped working on my "fork" of prosopopee is that I couldn't find a nice way to use Pillow in multi-threaded application with object-oriented programming. You can basically say bye to all your types (image, video, etc.) and use only a dict (from Manager) throughout the whole stack which is horrendous to maintain IMO. I'm happy to share my Proof-of-Concept and explain a bit what I've done and why if you're interested in it. |
No description provided.