[OSM-dev] Too many slow queries in db

Tom Hughes tom at compton.nu
Tue Sep 4 00:46:49 BST 2007

In message <1188862129.4515.91.camel at localhost.localdomain>
          Jon Burgess <jburgess777 at googlemail.com> wrote:

> On Tue, 2007-09-04 at 00:08 +0100, Tom Hughes wrote:
> > In message <200709040850140140.0A99AA0F at smtp.nsw.exemail.com.au>
> >           "Brent Easton" <b.easton at exemail.com.au> wrote:
> > 
> > > >Yeah sure. My magic query accelerator will sort it all out.
> > > >
> > > >Seriously, if you've got a magic way to make a database query
> > > >a 100 million row table in the blink of an eyelid I'll be only
> > > >to happy to deploy it.
> > > 
> > > So, what where the plans again to handle queries on a 2 billion row table
> > > post TIGER?
> > 
> > Um, we don't have one?
> > 
> > Seriously, I think it is (a) get a proper database and (b) find somebody
> > with sufficient experience of designing hardware and software solutions
> > for massive database to make it work.
> I'm still making progress with investigating a high speed tiger import
> process. It it too early to give any hard numbers but the signs are
> promising that we'll be able to achieve something significantly faster.

Getting it into the database isn't really the issue - in fact I would
probably prefer it to come in slowly so we have a chance to scale things
properly as it goes in.

The issue is having a usable database once the data is in, not getting
it in there.


Tom Hughes (tom at compton.nu)

More information about the dev mailing list