[OSM-talk] db stuff

[SteveC]

I've replicated the db on www. authentication selects, trackpoint api
etc are now served directly from there. This reduces by half the number
of queries to the main db but brings up other problems because www has
only half a gig of RAM. This has sped things up moderately for me with
small (applet-sized) areas.

There's not enough disk space on tile to do the same thing so it still
talks to db.

Joerg has offered to buy some ram for db. If anyone else wants to help
then nick hill is the guy to speak to, you can buy components direct and
have them shipped to him. If's he's still happy to sort it out :-)

transaction and locking documentation for ruby's mysql library is a
little thin on the ground. If anyone can find examples then that'd help
with re-writing some of the queries. Specifically, I can't find anything
documenting the use of commit() and how to build a chain of queries. An
entire seperate DB/tables for up to date data is starting to look more
reasonable though as it's a one-row update without one condition and an
insert rather than a two-condition update and an insert. It also makes
the select queries simpler, no condition on 'latest = 1'.

Regarding the GPX upload scripts: it's something that should be in the
API. Feel free to route around the lack of it.

Looking through the logs has highlighted the lack of favicon.ico for OSM
and FTP. If anyone can produce these that'd be super cool.

have fun,

SteveC steve at asklater.com http://www.asklater.com/steve/