[OSM-talk] Server slowness

[Kristian Thy]

On Mon, Jan 15, Nick Black wrote:
>> PostGIS, at least (I don't know much about MySQL's spatial abilities) has
>> GiST indexing, which is a nested polygon bounding-box index. If you have
>> geodata, why do you not store it in a geodatabase and get all the bells
>> and whistles for free, instead of trying to come up with a home-grown
>> solution?
> 
> Because it is more efficient, simpler and fulfills the tasks that OSM
> is trying to accomplish.

Yes, that is obvious from the performance of the server over the last
week. It is also obvious from the threads you link that you are totally
in control of the situation, and I will refrain from trying to help you.

> Sorry, I dont really follow this point.  OSM XML would still be needed
> to distribute data from the API, Planet, etc.  I dont think that the
> XML structure (itself always subject to reconsideration) forces the
> data structure.  Using  OSGEO Linestrings,  Multilinestrings however,
> would force the data-structure.

It's geometry, for $DEITY's sake. With attributes. There's nothing new
or special about the OSM data - it's the surveying that's the strong
point of the project. I see nothing in the OSM data that cannot be
portrayed with polylines, points and polygons.

> "Anyone who thinks the necessary technology is already out there to make
> OSM more efficient ought to prove it."[1]
> 
> [1] - 
> http://lists.openstreetmap.org/pipermail/dev/2006-September/002119.html

"I'm strapped to the backseat, so you can blame me for being a backseat
 driver all you want.  It's quite frustrating."[1]

[1] -
http://lists.openstreetmap.org/pipermail/dev/2006-September/002120.html

Anyway, since this is a discussion that seems to crop up from time to
time, perhaps Nick Hill's post you quoted should feature quite
prominently on the "Get involved" page on the wiki.

\\kristian
-- 
Cthulhu.call();