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

suggestion: configuration parameter for VRAM usage #41

Closed
teamolhuang opened this issue Oct 29, 2022 · 1 comment
Closed

suggestion: configuration parameter for VRAM usage #41

teamolhuang opened this issue Oct 29, 2022 · 1 comment

Comments

@teamolhuang
Copy link

teamolhuang commented Oct 29, 2022

I am using the latest release on Windows. I can use 2x and 3x without issue, but 4x always fail.

When I set tile-size to <= 65, error message vkAllocateMemory failed -10 shows up; when I set it above that or left the parameter out, the program starts up but then ends without any output result or warning message. It simply shows

image

and then just quits.

I am using a 6900XT with 16GB VRAM.

One thing I've observed from AMD panel while running the program is that it only goes up to ~4GB VRAM consumed before it quitted/showing error. Is there some way for the user to configure that the session should use more VRAM? RAM doesn't get consumed fully too.

GPU usage goes up to 100% before it quits abruptly so I think the process was started but somehow quitted without log. I also tried -j 1:1:1 but didn't help.

@teamolhuang
Copy link
Author

teamolhuang commented Oct 30, 2022

update: seems like it always exit out when it's at first gap sync gap3.
image
tested on 20220318 version so there is logging.

I've also find a weird behaviour when testing with waifu2x-ncnn-vulkan. On default setting for 4x same issue happens, but when I raised threads to like 16:16:16 it can run and complete things. It suprised me because usually I'd think less threads will be stabler??

Sadly the same trick didn't work on realcugan-ncnn-vulkan, though higher threads does show vkAllocateMemory failed -10. Through AMD panel, on something like 8:8:8, I saw VRAM being consumed to 8GB, but then it just exited. on 1:1:1 it consumed to ~1.3GB and then the program exit without any message.

But for now at least CPU mode is working for me in a reasonable time. Still looking for this issue's solution for GPU though.

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

No branches or pull requests

1 participant