Hi Juan I hope we could help you to manage 7 daily updates for the whole world.
There are several possible bottlenecks: * Updating and maintaining a region needs eventually the API because diffs assume that whole planet data is stored at the mirror (which exactly what we don't want when maintaining a region). And there is no fast API - there it's not even one available. * While initial import disks seem to be bottlenecks * While indexing and updating, it's perhaps CPU or memory. Pls. keep in touch about your experiences with OSM-in-a-box. Yours, S. 2011/1/26 Juan Lucas Domínguez Rubio <[email protected]>: > Dear list, > > I am trying to use Osm-in-a-box to keep a synchronized Postgis DB. > > I am doing a little test with the data of Iceland which should be about 0.06 > % of the whole OSM database (size of iceland.osm.bz2 is about 8 MB) and it > seems to be very slow (took 2 hours) > > The command was: > > sudo ./osm2gis.sh --initial-import -h localhost -d osmiceland -u postgres > -p postgres -f /mnt/data/iceland_25_01_2011.osm.bz2 > > With a simple rule of three, we should expect that the whole planet would > need 2 * 1600 = 3200 hours (about 4 months) to be imported. > > > Any general thoughts about Osm-in-a-box? > Anybody is keeping a synchronized DB by using OSM-in-a-box? > Is there a better mailing list than this to get help about this? > > > > Regards > Juan Lucas > > > > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev > _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
