Opened 17 years ago
Closed 16 years ago
#253 closed enhancement (wontfix)
Can geospatial_data use caching?
| Reported by: | nick | Owned by: | ole |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Efficiency and optimisation | Version: | |
| Severity: | minor | Keywords: | |
| Cc: |
Description (last modified by ole)
Currently geospatial_data object doesn't use caching. It would be beneficial for it to have caching especially when loading large datasets from 'pts' or 'txt' file.
What might be a good idea is to allow for a 'blocking' read-write. This would e.g. be useful for converting large csv files to pts files in case where the data won't fit in memory.
Change History (4)
comment:1 follow-up: ↓ 3 Changed 17 years ago by anonymous
comment:2 Changed 17 years ago by anonymous
baidu 163 sina beiing hotel hotel 太阳能4 star hotel2 star hotel 3 star hotel 5 star hotelwrought iron stair railings stair railings outdoor stair railings aluminum stair railing wrought iron stair baluster wrought iron stair railing parts staircase handrail iron stair rails interior metal staircase wood stair railings call center 4007 sell water
comment:3 in reply to: ↑ 1 Changed 17 years ago by ole
- Description modified (diff)
Replying to anonymous:
Caching may not help. If it is a matter of loading from a pts file or a cached result, the time it takes could be the same. It is worth investigating this, of course, so I'll leave the ticket open and get onto it at some point.
comment:4 Changed 16 years ago by ole
- Resolution set to wontfix
- Status changed from new to closed
I'll close this ticket since caching now works well for set_quantity.
Caching may not help. If it is a matter of loading from a pts file or a cached result, the time it takes could be the same. It is worth investigating this, of course, so I'll leave the ticket open and get onto it at some point.