mongodb - do any source-control systems use a document database for storage? -

One of those questions which is difficult for Google

We speed up our SVN repository on the second day Were running with. The standard solution for this is "more RAM! More CPU"! e.t.c. Which I got to think about, there is a source-control system that uses the document / nosql database (mongodeb, cochab etc.) for the database? It seems that this is a natural - but I'm not a specialist on the source-control database theory. Maybe to configure a more recent source control to use as a document DB storage The way?

Nobody who knows about me, and they do not want the difference in the degree of testing Given this, this will affect the debility (a really bad thing for a source code repository). Due to its inability to store delta, it will probably end the hurting performance.

Note that subversion has two very different storage mechanisms, supported by an embedded Berkeley DB, and supported by other simple files

apart from that, I understand quite a bit, then I will comment on Geett and TFS.

The use of the Geeta to store a lot of repository files efficiently packaged in the file system, the entire history is shorter than a checkout. For a very old project which is my laboratory, the whole history is 57 MB, and a working tree (not counting history) is 56 MB.

TFS stores a lot (probably all) of its data in the SQL database.