#6603 Certain code snapshots take forever even to queue up

v1.1.0
closed
General
2015-08-20
2013-08-26
No

Just to queue up a code snapshot, some requests take a really long time. E.g. https://sourceforge.net/p/texstudio/code/4175/tarball had the following timings. I've seen it with other high-revisioned SVN repos like sf.net/p/nhcontrib/code too.

{
    "mongo": 56,
    "repo.Commit.get_tree": 2,
    "repo.Commit.set_context": 0,
    "svn_tool.rev_parse": 138,
    "svn_tool._oid": 0,
    "repo.Commit.shorthand_id": 0,
    "total": 43615,
    "svn_tool.symbolics_for_commit": 0,
    "svn_tool.url_for_commit": 139,
    "sidebar": 144,
    "jinja": 16384,
    "svn_tool.__init__": 0,
    "svn_tool._path_to_root": 43138,
    "socket_write": 0,
    "socket_read": 36,
    "repo.Tree.set_context": 0,
    "svn_tool._revno": 0,
    "svn_tool.shorthand_for_commit": 0,
    "repo.Commit.url": 0,
    "svn_lib.info2": 43052,
    "ming": 97,
    "svn_tool.commit": 2
}

Discussion

  • Dave Brondsema

    Dave Brondsema - 2013-09-09
    • Size: --> 2
     
  • Dave Brondsema

    Dave Brondsema - 2013-09-09

    recurse & depth params to info2 could probably be changed to false.

    strace might be necessary to see what info2 is doing

    we could cache the result if needed

     
  • Dave Brondsema

    Dave Brondsema - 2013-09-09
    • Milestone: forge-sep-20 --> forge-oct-04
     
  • Dave Brondsema

    Dave Brondsema - 2013-09-20
    • Milestone: forge-oct-04 --> forge-oct-18
     
  • Dave Brondsema

    Dave Brondsema - 2013-10-04
    • Milestone: forge-oct-18 --> forge-nov-01
     
  • Cory Johns - 2013-10-24
    • status: open --> in-progress
    • assigned_to: Cory Johns
     
  • Cory Johns - 2013-10-25
    • status: in-progress --> code-review
     
  • Cory Johns - 2013-10-25

    allura:cj/6603

    Confirmed that adding recurse=False drops info2 time down from 27 sec to 0.01 sec and still functions as expected.

     
  • Dave Brondsema

    Dave Brondsema - 2013-10-25
    • status: code-review --> closed
    • QA: Dave Brondsema
     

Log in to post a comment.