-
Notifications
You must be signed in to change notification settings - Fork 126
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
Processing images is way to slow needs to be speed up #18
Comments
Hi 10/15 minutes is really too much time for a single image; are you sure that your gpu is used? The speed really depends on how big is your image; for example in my testing with a GTX 1660 with ~1080P image takes 10 seconds. What image resolution are you using? Windows 10 or Windows 11? Thank you for your feedback :) |
I am running 1440p resolution on Windows 10 original image size of the images I start with are like 3000x4000 or 4000x2500 |
Strange. With logic that your rx 6600 is faster than my 1660 so a 3000x4000 should take around ~1 minute in worst case. Maibe is something related to Pytorch with newer gpus, sadly I can't afford new Gpus to testing :( In any case try with something <1000x1000 just to test if works correctly :) (Should take ~30 seconds) |
I images that like 1200x2000 take max of like 90 seconds |
this is a good time, i will tweak some logic for VRAM limiter, that should be the problem while you wait for next release, try to set 6GB Vram and try a normal 3000x4000 :) |
Ok thx I will try out the next version |
Thank you :) |
The time it takes to process images with Qualityscaler is way to long it should not take 10 to 15 min to process any image. I have tested Quality vs Upscayl with Upscayl most images I can process it 3 or 4 times in the amount of time it takes Quality to process a image once this is the main negative thing about this program please take a look into this thx.
My video card is a RX 6600 I have 24gb DDR3 settings I use GPU and 6gb to 8gb Vram. My setup is pretty good for upscaling images.
The text was updated successfully, but these errors were encountered: