Opened 15 years ago

Closed 14 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: Changed 15 years ago by 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:3 in reply to: ↑ 1 Changed 15 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 14 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.

Note: See TracTickets for help on using tickets.