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

Opening N5 is slow #59

Open
StephanPreibisch opened this issue Jun 2, 2023 · 0 comments
Open

Opening N5 is slow #59

StephanPreibisch opened this issue Jun 2, 2023 · 0 comments

Comments

@StephanPreibisch
Copy link
Contributor

Hi, for me opening only uses a single thread more or less, which is not intended. Thus I was wondering how the LoopBuilder distributes tasks:

LoopBuilder.setImages( convImg, ipImg )
.multiThreaded( new DefaultTaskExecutor( exec ))
.forEachPixel( (x,y) -> y.set( x ));

Are maybe all processed pixels close to each other, so it wouldn't really open different blocks in parallel since all threads wait for the same block to be loaded?

Also, for virtual loading one should use multi-threading as well. ImageJFunctions.show does take a ExecutorService optionally for that ... we wrote this for BigStitcher some time ago. Because even if you load one z-plane virtually, you still need to load the entire blocks that are usually big in z.

Happy to help,
Stephan

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