loggerhead times out annotating large single files (eg sql_parse.cc from mysql-server)

[Christian Hammers]

Hello

http://bazaar.launchpad.net/~mysql/mysql-server/mysql-5.1/annotate/head%3A/sql/sql_parse.cc

repeatedly gives a:

  Please try again
  Sorry, there was a problem connecting to the Launchpad server.
  Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
  Thanks for your patience.

I tried a few days and 5 minutes ago with the same error. Other files from the same directory work. Maybe this file is just
too big (230k) or has had too many changes so that some kind of PHP memory_limit or Timeout is hit. Please fix!

bye,

-christian-

[Martin Pool (mbp)]

Confirmed today, so not connected to any transient problems with the rewrite map.

Christian, I suspect this file does have too long or complex of a history to be annotated within the cap on request time. Obviously it would be good to: annotate it faster, perhaps give partial data rather than total failure, or at least give a more useful message.

[Michael Hudson-Doyle (mwhudson)]

Yes, annotating this file seems to take at least 30 seconds, which is longer than the ProxyTimeout we give codebrowse.

It would perhaps be nice to have loggerhead only view files by default, and make the user click another link to get annotations. The current behaviour dates back to knits, when annotation information was almost free.

[Michael Hudson-Doyle (mwhudson)]

It's not a bug in loggerhead, per se. If you run loggerhead yourself, you'll get a page, just very slowly.

[Robert Collins (lifeless)]

Running slow is a problem ;)

[Robert Collins (lifeless)]

I'm upgrading this to critical - it would be triggering a timeout oops in the main website, and we want to make loggerhead a backend service, so this needs to be visible (and fixed)