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

Allow more explicit control over transaction lifetimes #34

Open
inexorabletash opened this Issue Aug 10, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@inexorabletash
Member

inexorabletash commented Aug 10, 2015

Imported from https://www.w3.org/Bugs/Public/show_bug.cgi?id=11528

Based on lots of developer feedback, in addition to the current automatic commit model it would be nice to support:

  • explicitly committing, to avoid extra round-trips (known performance bottleneck)
  • ways to defer committing to allow other async processing to occur within transaction scope

Both make the transaction model more complex, so we should tread carefully.

@inexorabletash

This comment has been minimized.

Show comment
Hide comment
Member

inexorabletash commented Aug 10, 2015

@inexorabletash inexorabletash referenced this issue Aug 10, 2015

Closed

Import issues from Bugzilla #15

14 of 14 tasks complete
@inexorabletash

This comment has been minimized.

Show comment
Hide comment
@inexorabletash

inexorabletash Sep 28, 2015

Member

In addition, for many puts, the overhead of all the individual success events can jank the main thread. We may want to design this in such a way that the transaction just opts-out of the per-request events entirely - possibly put() and friends just return null in those cases!

Member

inexorabletash commented Sep 28, 2015

In addition, for many puts, the overhead of all the individual success events can jank the main thread. We may want to design this in such a way that the transaction just opts-out of the per-request events entirely - possibly put() and friends just return null in those cases!

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