[OSM-dev] Mass imports (TIGER and AND)

[Dave Hansen]

On Tue, 2007-08-28 at 21:17 +0100, Steve Coast wrote:
> On 28 Aug 2007, at 19:23, Dave Hansen wrote:
> 
> > On Tue, 2007-08-28 at 19:06 +0100, Ray Booysen wrote:
> >> Will not moving some of the work out to seperate clients not solve  
> >> this
> >> problem?  With testing you're doing requests from one machine whereas
> >> the server should be able to handle multiple requests from multiple
> >> clients better.
> >
> > Parallelizing definitely does help.  Still, even if we got local-like
> > performance with 10 clients running and the server completely handled
> > that load without slowing down any of the clients, we're still looking
> > at over 6 months of continuous upload.
> >
> > I think a different approach is needed.
> 
> Given that OSM has 3 years without TIGER, will 6 months make all the  
> difference?

Well, that 6 months is a very, very optimistic guess.

> Also, loading it relatively slowly allows things like scaling to  
> occur smoother.

That's definitely true.  I don't have a particular problem with it
proceeding slowly.  I'm just being picky. :)

Today, it would be pretty easy to put my tiger-to-osm scripts together
with something that would dump the .osm result files into the API
instead of using JOSM.  Is 'dev' close physically to 'www'?  Would that
be an appropriate place to do this work?

-- Dave