[OSM-dev] Too many slow queries in db

Tom Hughes tom at compton.nu
Tue Sep 4 09:39:32 BST 2007


In message <8fcd02310709040135s2fbafec2h5e16ba057c19ddf0 at mail.gmail.com>
        80n80n at gmail.com wrote:

> On 9/4/07, Tom Hughes <tom at compton.nu> wrote:
>>
>> In message <20070904091233.p25hyf9pcg80goww at webmail.systemed.net>
>>         Richard Fairhurst <richard at systemed.net> wrote:
>>
>> > Tom Hughes wrote:
>> >
>> >> The issue is having a usable database once the data is in, not getting
>> >> it in there.
>> >
>> > It's only one very very little part of the problem, but we could move
>> > GPS traces to a different box.
>>
>> Not trivial in rails, but I believe it is possible.
>
> I don't understand why rails would be a constraint.  If you move the *whole*
> GPX solution to, say, gpx.openstreetmap.org then you have a completely
> separate rails instance as well.

Well it needs to tie to the user database, and I was assuming that
we would like to do it without making everybody change everything.

It's perfectly possible to do in rails, and when it is necessary
we can do it. It may even be a good idea once we have a new database
server to leave the GPX data on the old one for example.

Now if I could just manage to spend less time writing emails on this
subject and more time investigating solutions then something might
actually get done.

> In the short term, just turn off the whole GPX thing if it's slowing down
> the API.  We can live without it for a while.

The daemon has been turned off again this morning and is probably
going to have to stay off for the forseeable future in order to keep
the lock contention under control.

Tom

-- 
Tom Hughes (tom at compton.nu)
http://www.compton.nu/




More information about the dev mailing list