[OSM-talk] Errors on the API

[Ben Gimpert]

I'll defer to Steve on this decision, since he was the one that asked
for me to re-prioritize the TIGER import -- back around the new year.

		Cheers,
		Ben


On Tue,  6 Jun 06 @07:47am, Christian van den Bosch wrote:
> David Groom wrote:
> >How about stopping the TIGER import until the memory issues are fixed?
> >
> >I believe that to complete the TIGER import is going to take a matter of 
> >months, so if the import was stopped for a week, and so it then took 
> >months +1 week to finish, is it really going to matter.
> 
> I'm all for this, if the TIGER import is what's blocking people from 
> getting things done. Or if that doesn't appeal, could we perhaps make 
> the import more responsive to server load in some way - perhaps a sleep 
> after each transaction, (some multiple of) the time it took to complete? 
> This would - hopefully - mean that the import doesn't consume more than 
> some fixed fraction of free CPU on the server, averaged over a few 
> transactions. Evaluating and limiting memory usage from the client side 
> will be trickier. Ben?
> 
> Right now I can't get anything done with respect to mapping my area. The 
> API has been broken every time I tried it in the last day or so, the 
> applet is unusably slow, and without having a recent planet dump to 
> print out a map from, I can't even figure out where to go GPSing...
> 
> Christian / cjb
> 
> http://www.cjb.ie/