Version support for datastore/Progress: Difference between revisions
Sascha silbe (talk | contribs) final benchmark run |
Sascha silbe (talk | contribs) m →2009-06-08: fix typo |
||
| Line 122: | Line 122: | ||
to scale well with branches (both size and runtime) and also has the highest memory consumption. | to scale well with branches (both size and runtime) and also has the highest memory consumption. | ||
The results emphasize need to use an abstraction layer so we can switch between different VCSs (depending on what resource is | The results emphasize the need to use an abstraction layer so we can switch between different VCSs (depending on what resource is | ||
scarcest) or even to a homegrown backend later. For the prototype git seems to be a good candidate as it combines average | scarcest) or even to a homegrown backend later. For the prototype git seems to be a good candidate as it combines average | ||
resource consumption with a rich API, including low-level access. | resource consumption with a rich API, including low-level access. | ||