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

draw_sync thread model causes full synchronization #88

Closed
eile opened this issue Jan 31, 2012 · 2 comments
Closed

draw_sync thread model causes full synchronization #88

eile opened this issue Jan 31, 2012 · 2 comments
Assignees
Milestone

Comments

@eile
Copy link
Member

eile commented Jan 31, 2012

when running eqPly with the draw_sync thread model, all nodes are fully synchronized.

@ghost ghost assigned eile Jan 31, 2012
@eile
Copy link
Member Author

eile commented Feb 1, 2012

Works as designed:

An implication of the draw_sync and local_sync models is that the application node can not issue a new frame until it has completed all its draw tasks. For larger cluster configurations it is therefore advisable to assign only assemble operations to the application node. If the machine running the application process should also contribute for rendering, a second node may be used to perform off-screen draw and readback operations for the application node process.

@eile eile closed this as completed Feb 1, 2012
eile added a commit that referenced this issue Feb 1, 2012
- found during #88

[ ] May break build
[ ] May break existing applications (see CHANGES.txt)
[x] Bugfix
[ ] New Feature
[ ] Cleanup
[ ] Optimization
[ ] Documentation
@eile
Copy link
Member Author

eile commented Feb 1, 2012

The pipe finish draw arrives after the frameAssemble for an appNode with no draw tasks.

@eile eile reopened this Feb 1, 2012
@eile eile closed this as completed in 94a5f23 Feb 1, 2012
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