[OSM-dev] [PATCH] Persistant database connection

[Lars Aronsson]

James Mastros wrote:

> Currently, the core of OSM is a bit silly: Every time it wants to execute
> some SQL, it connects to the database, runs the sql, gets the entire result
> set, and then disconnects from the database.  There's a number of ways in
> which that's silly, but the simplest one is that there's no reason to keep
> connecting and disconnecting -- connect when you first need the connection,
> and disconnect when you're all done.

Apart from there is no reason to disconnect and connect again, is 
there any reason to implement the change?  Because you say it's 
silly, or because it will actually make things faster or better?  
How much faster or better?  Do you have numbers, do you have an 
estimate, or can you tell how we can get numbers?

I'm not a developer here, so my comments have absolutely no 
influence on anything.  But I am a developer by profession, and I 
prefer measurement over guesswork.  If anything, I'd like to get 
that mindset into OSM.

Right now I'm editing maps in Norway, using the Java applet.  
Despite Steve's recent announcement that everything should be 
faster now after this Saturday's improvements, the website feels 
just as slow to me as it did last week.  I'm not living what I 
preach, since I only "feel" the slowness.  I have no hard numbers 
to prove my point, and I'm feeling guilty for that.

I vaguely remember a webhoster telling me (to my surprise at the 
time) that they recommend *against* persistent MySQL connections, 
but I can't remember why or what version of MySQL that was.  Does 
your change leave connections open across HTTP calls?


-- 
  Lars Aronsson (lars at aronsson.se)
  Aronsson Datateknik - http://aronsson.se