Opened 20 years ago
Last modified 10 years ago
#2636 new enhancement
browsing a directory with many files takes a long time
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | version control/browser | Version: | 0.9.3 |
| Severity: | normal | Keywords: | performance |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
when browsing a repository browser with a lot of files (tested with 3370) it takes a long time (minutes) before the files are shown in the browser.
enhancement: It would be better to limit the amount of files processed, as to process them in blocks (configurable, default 250?)
tested with gentoo-linux on a P4 2.4GHz 512MB RAM with apache and fastcgi (5 preforks) as interface to trac (0.9.3) (all processing power was available to trac at that moment)
client is windows xp with firefox 1.5.0.1
Attachments (0)
Change History (6)
comment:1 by , 20 years ago
comment:2 by , 19 years ago
| Milestone: | → 0.11 |
|---|
This will probably be much improved using the new cache scheme.
comment:3 by , 19 years ago
| Owner: | changed from to |
|---|
comment:5 by , 16 years ago
| Keywords: | performance added |
|---|
See also #6101, which proposes paging.
This ticket is about trying a different approach, relying on the cache (node_change table) in order to get a speedup for Node.get_entries().
comment:6 by , 10 years ago
| Owner: | removed |
|---|
See also #2591, similar request for enhancement about the changeset view