nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Speed up downloading a review from fisheye

klas_klassen

I use Atlassian fisheye for code-review. If I create a review which has about 2000 revisions and 1700 files it takes a very long time to download the revision. If I open the Chrome developer tools "Network" I see that it consumes 12 minutes for about 800 Kb. But a first it waits 2 minutes before it starts downloading.

Does anyone know how to speed the process up? Either tuning Chrome or Fisheye?

Details: I look at the server where Fisheye is running, everything looks OK. Not memory, CPU or harddisk overuses. Server and Chrome are in the same company network. I selected only whole file and files which have not been deleted

Accepted answers

Maciej Swinarski

Hi Klas,

This is a pretty big review. We usually recommend creating few smaller reviews covering changes that need to be reviewed. What version of Crucible are you using?

mac

All comments

Maciej Swinarski

Hi Klas,

This is a pretty big review. We usually recommend creating few smaller reviews covering changes that need to be reviewed. What version of Crucible are you using?

mac

klas_klassen

We are using fisheye (Version:3.7.0 Build:20150127093303) . We have this big reviews because we make a complete review over all files of a module once or twice a year. For every pull-reuest we create a small code-review is already done via Atlassian Stash

Maciej Swinarski

I would recommend upgrading to newest Crucible. There were many performance improvements since 3.7. If the problem continuous I would recommend: turning debug ON, load a large review and create a case with the support zip, so we can look into the problem.

klas_klassen

updating to 3.10 solved the problem. it still needs about a minute to load but that is okay.