[OSM-dev] Planet file space requirements

Linden Varley Linden.Varley at ardec.com.au
Fri Oct 30 00:12:27 GMT 2009


I disagree. Weekly writes to the SSD will not be that bad and the performance benefits far outweighs the disadvantages. We can do a full planet file load in 4 hours and database reads are outstanding to the point where it's not even necessary to pre-cache tiles.

- Linden

-----Original Message-----
From: Stefan de Konink [mailto:stefan at konink.de]
Sent: Friday, 30 October 2009 9:56 AM
To: Linden Varley
Cc: Frederik Ramm; dev at openstreetmap.org
Subject: Re: [OSM-dev] Planet file space requirements

On Fri, 30 Oct 2009, Linden Varley wrote:

> Is there potential to be able to do differential updates on a non-slim imported db?
>
> Reason I ask is I have plenty of memory, but little DB space (SSD) and I would like to do weekly diffs, import with osm2pgsql and get a tile expiry list to re-cache changed tiles.
>
> If not, I'll import with slim on a larger disk and do a filesystem copy across to the SSD.

I rather suggest to ditch the SSD, the chances that it will be killed (in
performance) are rather high with non-static datasets as OSM.


Stefan


The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.




More information about the dev mailing list