[Geocoding] osm2pgsql / Gazetteer import errors

[Frans Hals]

Andy,

thank you for your valuable input.
Do you think, that running (not importing) the database will be still slow
at EC2?
I liked the idea of using some kind of load balancing (one machine online,
one offline for upgrading indexes) which will be easily set up with the
cloning feature.
Your EC2 experience doesn't sound very promising for achieving this goal.
Do you know another faster host which has this cloning feature?

Regards
Frans

2010/1/4 Andy Allan <gravitystorm at gmail.com>

> On Mon, Jan 4, 2010 at 2:52 PM, Brian Quinion
> <openstreetmap at brian.quinion.co.uk> wrote:
>
> >> I started the process on a standard Amazon cloud 32-bit 1-Processor
> Fedora unit.
> >
> > Not any immediate problem but I'd guess due to the size of node IDs a
> > 32 bit machine has a limited time left - I'd guess around 2 years.
>
> So Amazon EC2 machines have stunningly dreadful disk performance. It's
> a continual headache that I'm running the cyclemap on one (an
> extra-large instance). I use "normal" mode for the cyclemap import,
> but Matt used to use slim mode for his minutely tileserver and it
> would take about a week to just run osm2pgsql (I'll let him correct me
> if that's wrong). Although I haven't used the gazetteer import mode on
> one, I can't imagine for a minute that it'll be in any way quick.
>
> My advice would be to find another host other than EC2 if you are
> doing anything involving osm2pgsql (or anything else that isn't
> running in RAM).
>
> Cheers,
> Andy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20100104/5ac850b1/attachment.html>