Closed GoogleCodeExporter closed 9 years ago
The patch itself isn't too big, so the slowdown is likely due to accessing the
files
from the repository. Once this is done once, it should be cached for a while.
I'm not
sure why it would be so slow for you. At VMware, we have a thousand engineers
using
Review Board for patches up to 4MB in size across about 10 repositories and
aren't
having the slowdown you're seeing.
What cache backend is being used there, and what repository type?
Also, how recent is the server? Some time ago we added support for paginating
the
diffs so that we only dealt with a certain number of files at a time. It should
be
helping, so we need to find out why it's not.
Original comment by chip...@gmail.com
on 30 Jul 2008 at 4:24
C - Great questions. For now, let's just close this bug then and I'll reopen
if it
proves to be RB. Thanks :-)
Original comment by kevin.be...@beatport.com
on 30 Jul 2008 at 5:23
Sure thing.
Original comment by trowb...@gmail.com
on 30 Jul 2008 at 5:28
Original issue reported on code.google.com by
kevin.be...@beatport.com
on 30 Jul 2008 at 3:46