You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today i found https://sharp.pixelplumbing.com/ and after reading i found your cli version. I am impressed by the results, it works great. Now i am running it on thousands of images and i wonder why it does not use the full power of my 16 cores 5950x. Load in htop looks pretty low. Is there anything i could do?
I found no switch to set a core-count, or something.
Regards.
Not sure if its an "issue"...
The text was updated successfully, but these errors were encountered:
Today i found https://sharp.pixelplumbing.com/ and after reading i found your cli version. I am impressed by the results, it works great. Now i am running it on thousands of images and i wonder why it does not use the full power of my 16 cores 5950x. Load in htop looks pretty low. Is there anything i could do? I found no switch to set a core-count, or something.
Regards. Not sure if its an "issue"...
What are you experiencing / expecting? Does it take too long?
The CLI invokes the sharp pipeline for (all) images in parallel, but I'm not sure about further specifics on how sharp deals with that - maybe this is helpful?
Hm, does it take long... Thats relative ;).
I am running it over thousands of images while merging a project from old to new software. And i was curious if there might be some performance switches i might have overseen.
I just want my 16 cores to be used like when they compile.
Today i found https://sharp.pixelplumbing.com/ and after reading i found your cli version. I am impressed by the results, it works great. Now i am running it on thousands of images and i wonder why it does not use the full power of my 16 cores 5950x. Load in htop looks pretty low. Is there anything i could do?
I found no switch to set a core-count, or something.
Regards.
Not sure if its an "issue"...
The text was updated successfully, but these errors were encountered: