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

Topology afterCommit and afterRollback optimization #139

Closed
pietermartin opened this issue Jan 15, 2017 · 0 comments
Closed

Topology afterCommit and afterRollback optimization #139

pietermartin opened this issue Jan 15, 2017 · 0 comments
Assignees

Comments

@pietermartin
Copy link
Owner

The current Topology.afterCommit and Topology.afterRollback iterates the whole topology every time.
This is rather inefficient especially on large topologies. It is also rather stupid as the topology only needs to be iterated and managed when the write lock is held by the current thread.

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

No branches or pull requests

1 participant