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

[BREAKING] perf(Transactions): Run transactions concurrently #7694

Merged
merged 26 commits into from
Apr 10, 2021

Conversation

manishrjain
Copy link
Contributor

@manishrjain manishrjain commented Apr 7, 2021

This PR introduced concurrent mutation processing. It does so in this way:

  • We receive a txn with mutation at start ts = Ts.
  • The server is at MaxAssignedTs Tm < Ts.
  • Before, we would block proposing until Tm >= Ts. This PR changes that.
  • Now, we propose the mutation immediately.
  • Once the mutation goes through raft, it is executed concurrently, and the "seen" MaxAssignedTs is registered as Tm-seen.
  • The same mutation is also pushed to applyCh, like we do today.
  • When applyCh sees the mutation, it checks if any reads the txn incurred, have been written to with a commit ts in the range (Tm-seen, Ts]. If so, the mutation is re-run.
  • If no commits have happened for the read key set, we are done.
  • If multiple mutations happen for the same txn, the sequential mutations are always run serially by applyCh. This is to avoid edge cases.

This sequence improves the 75-th %-ile latency of mutations from 30ms down to 1ms. The 21M live loader dataset gets loaded on my workstation in 8 mins.

Given these improvements, I've removed ludicrous mode, which was buggy. This PR also contains a bug fix for how we were handling filterStringFunction.


This change is Reviewable

@github-actions github-actions bot added the area/testing Testing related issues label Apr 7, 2021
@manishrjain manishrjain marked this pull request as ready for review April 9, 2021 06:08
@manishrjain manishrjain changed the title opt(Transactions): Run transactions concurrently perf(Transactions): Run transactions concurrently Apr 9, 2021
@manishrjain manishrjain changed the title perf(Transactions): Run transactions concurrently [BREAKING] perf(Transactions): Run transactions concurrently Apr 10, 2021
@manishrjain manishrjain merged commit dd6bcb8 into master Apr 10, 2021
@manishrjain manishrjain deleted the mrjn/conc-apply-ch branch April 10, 2021 13:12
manishrjain added a commit that referenced this pull request May 5, 2021
In this PR, we use concurrent mutations system, introduced in #7694 , to generate Skiplists directly from a transaction, even before it is committed.

When a transaction does get committed, we replace the key timestamps with the commit timestamp, in-place within the Skiplist. And in case of multiple transactions being committed, merge them together into one bigger Skiplist during the serial commit.

This Skiplist is then handed over to Badger, bypassing its value log and WAL system. Instead, when Badger persists the skiplist into L0 tables, Dgraph gets a callback, which it uses to decide when it is safe to take a Raft snapshot / checkpoint. So, we no longer need Badger's WAL.

Furthermore, live loader is also optimized to better deal with the conflicting transactions, and retrying them as frequently as possible, instead of only towards the end. The updated output from live loader shows we're able to deal with stragglers much better, with them causing almost no delays with this PR.

There's also a bug fix in this PR. The Raft checkpointing code was not getting run as often as it should. This PR fixes that.

```
Master:
[18:48:34-0700] Elapsed: 08m45s Txns: 21222 N-Quads: 21,221,870 N-Quads/s: 9,033 Aborts: 0
Number of TXs run            : 21240
Number of N-Quads processed  : 21239870
Time spent                   : 8m49.039284385s
N-Quads processed per second : 40150

This PR:
Number of TXs run            : 21240
Number of N-Quads processed  : 21239870
Time spent                   : 6m56.641399434s
N-Quads processed per second : 51057
```

Notable Changes:
* Have each mutation create its own skiplist. Merge them during commit.
* Use skiplist Builder
* optimize mutations as well
* Optimize live loader to better deal with conflicted requests.
* Make a callback delete txns from Oracle.
* Bug fix: Calculate raft checkpoint frequently.
* Clarify snapshot rules.
* Incremental rollups use skiplists too.
* Stop rollups during drop operations.

Co-authored-by: Ahsan Barkati <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Testing related issues
Development

Successfully merging this pull request may close these issues.

2 participants