On 01/13/2012 04:36 PM, Tim Alder wrote:
Hello, I see also no problem to use hikebikemap over a caching-server, as long as you keep under 10 Tilerequest/sec in average and 100 Tilerequests/sec in peak. I hope that's ok for you, else we need to talk.
(We deliver in the moment nearly 100 Tiles/sec, but we can deliver more.)
From a technical point of view, I would guess the server could handle
quite a bit more than the 100 - 200 Tiles / sec it currently delivers.
For tiles that are in Ram (e.g. in a benchmark that always hits the same tile), upwards of 1000 Tiles / sec shouldn't be too much of a problem, but once again the limiting factor is likely to be disk access.
The tiles are currently stored on a shared storage array connected via nfs, which is shared across many toolserver users. I don't currently have a good handle on how much resources the tile server is using up from the array and how much it can expand before effecting other users adversely, but I hope there is still some room left.
It is hard to judge how many tile requests 100.000 "API calls" will result in. A typical full screen map will probably need somewhere around 30 - 40 tiles per screen. So it may result in 10 - 100 tiles/sec on average, presumably more during the day.
Caching will then help limit the numbers again for access to the toolserver. It is hard to predict how high hit ratios will be as it depends on a lot of factors. The osm.org proxy has if I am not mistaken a hit ratio of about 30 - 60 % hit ratio. Back in 2008(?) when tile expiry was still once a week rather than minutely, hit ratios were more in the 80% range if I remember correctly. Given that GPSies has a limited area, hit ratios might be higher.
Even though these calculations are all rather vague and could easily be off by an order of magnitude, I would say it probably ends up being a significant load compared to currently, but one that technically probably can be handled. It would probably need some real testing though to get a better handle on exact numbers and how it will all behave.
If the thing is only temporary until your own servers are in place, it might actually be an interesting load test to get a better feeling for if it can handle the osm gadget being activated in the en wikipedia.
Kai
Greetings Kolossos
Am 13.01.2012 20:27, schrieb Klaus Bechtold:
Hello everyone,
my name is Klaus Bechtold from Berlin, the guy behind the hobby project and one-man-show GPSies.com (http://www.gpsies.com/). As you know, many of the map mashups or community must change from Google Maps to alternatives (because we're over the limit of 25.000 API calls a day).
I just changed to the new JS API from Cloudmade, called Leaflet and I am using the free MapQuest maps (which are good, but not good enough for outdoor people). I'm also using also some other maps, like OpenCycleMaps or the great hikebike maps of Colin Marquardt.
Next time I'm planning to produce own tiles for GPSies.com. The (3 new) servers are running and we must now configure it, but this will take some time.
Now to my question. I just called Colin (hikebikemap.org) and I asked him, if GPSies.com (only the website, no mobile devices) could deliver the tiles by a caching proxy of hikebikemap.org - as the new standard maps of GPSies.com. Colin said, he had no problem with it, but I should ask you, if it would be ok for the load and traffic of the toolserver tileserver.
GPSies has about 30.000 (winter) to 100.000 (sommer) page views with maps a day. Most of the users are from Germany (50%). Most of the tracks are from almost the same regions.
I'd be appreciate, if you would allow my the tiles caching of your server. I also like to donate.
Thanks!
Best regards from Berlin, Germany
Klaus Bechtold
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l
Maps-l mailing list Maps-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/maps-l