Opened 7 years ago
Closed 7 years ago
#12765 closed defect (fixed)
Downloading a zip archive from browser page eats huge memory — at Version 3
| Reported by: | Jun Omae | Owned by: | Jun Omae |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0.14 |
| Component: | version control | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: |
Use a temporary file to create a zip archive and send a streaming zip archive. |
||
| API Changes: | |||
| Internal Changes: | |||
Description
Currently, a zip file from browser page is created in memory. If a changeset or a repository is large, it would eat huge memory.
I consider we should use tempfile to create a zip archive rather than memory.
Change History (3)
comment:1 by , 7 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 7 years ago
If the created zip archive is large, it would be waited to start response in long time. It might be lead to time out.
I think we should start to respond before finish of creating the zip archive → [a0155666c/jomae.git] (jomae.git@t12765-streaming).
comment:3 by , 7 years ago
| Release Notes: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Committed in [15831,15833-15834] and merged in [15835-15836].
Note:
See TracTickets
for help on using tickets.
Proposed changes in [5d1ca0500/jomae.git] ([log:jomae.git@t12765).