#5094 Don't build CommitRunDocs for SVN repos

forge-oct-19
closed
Cory Johns
General
2
2012-10-19
2012-10-09
Cory Johns
No

In [#5046], it was discovered that one of the sources of slow queries against the repo_commitrun table was getmore operations against very large CommitRunDoc records, which are almost entirely from SVN repos.

SVN commit histories are entirely linear, so the entire history ends up in a single CommitRunDoc. This is slow and pointless.

Modify the SVN implementation to not create or use CommitRunDocs, instead leveraging the fact that the histories are inherently linear.

Related

Tickets: #5046
Tickets: #5121
Tickets: #5123
Tickets: #5143

Discussion

1 2 > >> (Page 1 of 2)
  • Dave Brondsema
    Dave Brondsema
    2012-10-11

    An alternate approach to alleviating the affect of these slow queries is to force them to run from a slave. That will prevent them from holding up other queries on the master. However, slaves may be slightly out of date, so we need to make sure we don't introduce race conditions or conflicts/clobberings.

     
  • Cory Johns
    Cory Johns
    2012-10-15

    • status: open --> code-review
    • assigned_to: Cory Johns
    • qa: Dave Brondsema
    • size: --> 2
     
  • Cory Johns
    Cory Johns
    2012-10-16

    allura:cj/5094

    Paging wasn't being applied correctly when generating the commit history for any type of repo.

    Easiest way to test is on a sandbox with an up-to-date copy of production mongo; you can use cjohns-6049 if you like.

     
1 2 > >> (Page 1 of 2)


Anonymous


Cancel   Add attachments