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

Inappropriate block size for ScanConverterNode #94

Open
xiaoyun2 opened this issue Jan 15, 2020 · 1 comment
Open

Inappropriate block size for ScanConverterNode #94

xiaoyun2 opened this issue Jan 15, 2020 · 1 comment

Comments

@xiaoyun2
Copy link

I try to change the block size of ScanConverterNode from (1,256) to (16,8) which reach a great performance improvements in my side GTX 1080, 1.2ms to 0.3ms and TX2 25.50ms to 3.16ms.
So this may be common that current block size cause performance drop.

@goeblr
Copy link
Member

goeblr commented Feb 18, 2020

Oh wow!
Yes, I didn't fully tune all the block-sizes.
Is this with 2D imaging?

If you are doing any more tweaks, I'm happy to incorporate a pull-request :)

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

2 participants