Opened 18 years ago
Last modified 15 months ago
#5499 new defect
performance issues when viewing larger files
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-stable-1.6.x |
Component: | version control/browser | Version: | devel |
Severity: | normal | Keywords: | blame performance |
Cc: | kirean@…, Jun Omae | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
There are numerous source code files in our project that are above the default limit (250kB).
When viewing these files, it takes a moment before they're generated and rendered by the browser. When using the 'annotate' option, this problem increases significantly. Here is a sample (server is a P733, using apache):
Original size: 200kB
Browser view: 800kB, generating time: 1 minute
Annotated view: 1500kB, generating time: 5 minutes
It gets far worse on files that are 400+kB (actually I don't even try that anymore).
Additionally, when viewing such an annotated page in Opera, the browser does 100% cpu load that doesn't stop until you close the page. Sometimes it also destabilizes the browser (needs restart).
Can anything be done in this regard?
Attachments (0)
Change History (13)
comment:1 by , 18 years ago
Keywords: | blame added |
---|---|
Milestone: | → 0.11 |
comment:3 by , 17 years ago
The annotate view in 0.11 looks cool, but if performance is effected I'll be stuck with ViewVC anyway. I would prefer this to be done in the same (fast) way as in ViewVC instead..
comment:4 by , 17 years ago
Well, until the performance issue gets fixed, maybe we could try to disable the javascript code for anything but small files:
-
trac/versioncontrol/templates/browser.html
27 27 range_max_secs: '$dir.range_max_secs' 28 28 }); 29 29 </py:if> 30 <py:if test="file and file.annotate ">30 <py:if test="file and file.annotate and file.size < 50000"> 31 31 enableBlame("${href.changeset()}/", "${path}"); 32 32 </py:if> 33 33 });
I doubt this will be enough to fix the performance issue, but maybe it will make it more acceptable.
comment:6 by , 15 years ago
Milestone: | 0.12 → next-minor-0.12.x |
---|
comment:7 by , 11 years ago
Cc: | added |
---|
comment:8 by , 10 years ago
Milestone: | next-minor-0.12.x → next-stable-1.0.x |
---|
comment:9 by , 10 years ago
Keywords: | performance added |
---|
comment:10 by , 10 years ago
Owner: | removed |
---|
comment:11 by , 8 years ago
Milestone: | next-stable-1.0.x → next-stable-1.2.x |
---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:12 by , 5 years ago
Milestone: | next-stable-1.2.x → next-stable-1.4.x |
---|
There's certainly room for improvement:
Tentatively scheduling for 0.11.