On a development note, Dan Ramage was working with HF Radar datasets recently and was pushing the data to a sqlite database table and mapping via MapServer/OGR and OpenLayers.
Dan was collecting a days worth of data in the same table, but only wanted to map the most recent data. The performance issue we ran into for this case is that as MapServer/OGR does not support general database indexes for query (like an index on the time column) only supporting spatial indexes or attribute indexes for shapefiles. This results in a slow performing query/map render as MapServer/OGR was performing a full table scan(reading all table rows).
The solution to getting around this issue is to utilize a database view which represents an indexed subselect on the table data which is of interest - in this case the table rows which had been flagged 'recent' by an indexed column field/attribute. MapServer/OGR references the view resulting in greatly improved performance. In the past we have also generated separate tables(map tables) or hourly shapefiles, but the view approach allows us to achieve that subset query performance without having to physically split data out from the initial tables.
In addition to indexes on time columns, crude spatial indexes on longitude and latitude, or observation/measurement type columns could also be specified and utilized in a database view to support faster MapServer/OGR subset query/render.
Jeremy