[OSM-dev] API very slow this morning
styno at hotmail.com
Thu Mar 22 13:16:49 GMT 2007
I can reverse it: If you don't have anything constructive to say, just
MySQL itself says  that the MyISAM storage engine is not the best
choice - for situations where the portion of update/delete statements is
significant in relation to insert and select statements - because of the
table locking mechanism. So why spending effort to work around the
database 'restriction' when this fundamentally important part of the
project is ill chosen?
I've also tried to make my point in the wiki  earlier. Now please
tell me why my arguments are not valid, that way I can perhaps learn
something out of this.
Kristian Thy wrote:
> On Thu, Mar 22, Styno wrote:
>> Summary: Please do not try to optimize code to work around a problem
>> embedded in the chosen database. Fix the database instead.
> ObOSMResponse: Prove it before we will listen to you.
More information about the dev