[OSM-dev] Proposal: Database accelerator and dirty tile marker based on simple algorithm.
Andy Robinson
Andy_J_Robinson at blueyonder.co.uk
Thu Sep 21 10:36:36 BST 2006
Nick,
The Munin graphs appear to show the server being powered down or at least
not talking to the Munin log quite a lot throughout this week. Most
noticeable on the cpu plots. Is there a specific reason for that? The
behaviour is not there on previous weeks.
Cheers
Andy
Andy Robinson
Andy_J_Robinson at blueyonder.co.uk
>-----Original Message-----
>From: dev-bounces at openstreetmap.org [mailto:dev-bounces at openstreetmap.org]
>On Behalf Of Nick Hill
>Sent: 21 September 2006 9:43 AM
>To: dev at openstreetmap.org
>Subject: Re: [OSM-dev] Proposal: Database accelerator and dirty tile marker
>based on simple algorithm.
>
>Hello Lars
>
>Lars Aronsson wrote:
>> What I see here is urban legends, myths and guesswork. Yes, you
>> made some changes to the SQL, for example on August 31. But what
>> was the load before that and how did it change afterwards? I see
>> no statistics at all on how many requests are served. So how can
>> you say that "demand" has increased? My guess is that since the
>> system appears to be slower, you guess that demand has increased.
>> Since I don't like to guess, I'm asking: What do you base this
>> statement on?
>
>The rate of growth in dataset is a pretty good indication that the
>number of requests served accelerated and functionality of the system
>has lowered bottlenecks since installing the new systems.
>
>When the system was transferred, the dataset was around 4Gb. Today it
>stands at around 13Gb. Nearly 1.3Gb has been shaved off the GPS point
>database through efficiency measures, making the total today the
>equivalent of 14.3Gb. Grown by 3.5 times in 4.5 months.
>
>>
>> Now the tile server works so-so on some days and is completely
>> dead on other days, but the reason is a complete unknown. All I
>> know for sure is that *I* am not trusted with a login account on
>> the tile server, so *I* cannot look in the log files what's going
>> on. I'm strapped to the backseat, so you can blame me for being a
>> backseat driver all you want. It's quite frustrating.
>
>We do have data from munin.
>http://www.openstreetmap.org/munin/openstreetmap/tile.openstreetmap.html
>Any data needs to be analysed and interpreted. From experience, I can
>interpret those graphs with a fair degree of confidence.
>
>>
>>> Looking for method changes which can improve performance
>>> possibly by another order of magnitude is really what we need.
>>
>> No, what we need is measurement. How many calls are served, how
>> much time does each call take, and what part of the call is taking
>> time? Without measurement, every change is a guesswork.
>
>Measuring calls on tile would not yield useful results because you will
>not be measuring the call you are making in terms of processing load.
>You will instead be measuring the background system load. We already
>have that data. If you are a scholar of science, you will know that we
>need controlled experiments. Experiments which isolate external effects.
>
>If you would like to implement the tile server rendering functionality
>at home against the planet data set, it should be pretty obvious where
>the bottlenecks are.
>
>I would welcome your suggestions how to improve the performance of tile
>or submit optimised code.
>
>
>
>
>
>
>_______________________________________________
>dev mailing list
>dev at openstreetmap.org
>http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.405 / Virus Database: 268.12.6/453 - Release Date: 20/09/2006
>
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.6/453 - Release Date: 20/09/2006
More information about the dev
mailing list