Yes, I saw similar ideas ~ a year ago, & figured it was possible. It was just a matter of using sqlite's (excellent) sqldiff utility and wrapping a custom git diff driver. Took about an evening to get the proof-of-concept working and a little more fiddling for ease of use.
I don't have stress test results, but it should be similar to git. I think I remember getting it up to several hundred megabytes at one point and it was fine. I mostly use it for smaller sets of highly relational data that I want to track like I would source code.
By leveraging git & sqlite it lets me avoid writing a network sync implementation, architecture specific code, or patching any C code to recompile.
Instead of storing the transactions as a separate lmdb commit, I decided to store the database in a git repository and expose the diffs using sqlite's sqldiff utility. This allowed my workflow to be almost unchanged and limits the dependencies to git, sqlite, sqldiff, & bash.
If people are a little confused about what this does, it lets you track a sqlite database using git. If a change is detected to the database, the diff is the set of sql queries necessary to mutate the database from one state to the next.
I have found it to be extremely useful for certain problems.
Remote: Yes
Willing to relocate: Maybe
Technologies: BQN, Erlang, C
Résumé/CV: email me
Email: my username at gmail dot com