#7256 closed defect (fixed)
"flush tile cache" takes forever
| Reported by: | NE2 | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | 15.05 |
| Component: | Core imagery | Version: | |
| Keywords: | cache | Cc: | bhil@… |
Description
A change was made recently to have this delete all the tiles on disk. On Windows XP, this can take hours. I don't know if there's a solution, but some sort of warning at least would be nice.
Attachments (0)
Change History (21)
comment:1 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Reopened - the cancel button doesn't work.
comment:4 by , 13 years ago
| Cc: | added |
|---|
comment:5 by , 13 years ago
Please note that the long duration could be appropriate - presently the cache on my machine is 4.5 GB consisting of almost a million files (in one single directory!). When I submitted defect #8126, the cache was even bigger.
comment:6 by , 12 years ago
| Component: | Core → Core imagery |
|---|
comment:7 by , 12 years ago
Why not store the tiles in an sqlite database instead of dumping a million files to the disk which take an hour to delete?
comment:8 by , 12 years ago
| Milestone: | → 14.05 |
|---|
comment:9 by , 12 years ago
| Keywords: | cache added |
|---|
comment:10 by , 12 years ago
| Milestone: | 14.05 → 14.06 |
|---|
Move imagery cache-related tickets to next milestone (too risky now for this release)
comment:11 by , 12 years ago
| Milestone: | 14.06 → 14.07 |
|---|
Move all tickets for which no work has been done yet to next milestone
comment:14 by , 11 years ago
| Milestone: | 14.09 → 14.10 |
|---|
Move complicated/risky tickets to next milestone.
comment:15 by , 11 years ago
| Milestone: | 14.10 → 14.11 |
|---|
Not enough time/resources for these tickets this month.
comment:16 by , 11 years ago
| Milestone: | 14.11 → 14.12 |
|---|
comment:19 by , 11 years ago
| Milestone: | 15.02 |
|---|
comment:20 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
This should be fixed, at least for TMS layer.
comment:21 by , 11 years ago
| Milestone: | → 15.05 |
|---|
In 4985/josm: