|
We are looking to roll our own OSM server, and are currently trying to lay down some basic server requirements in terms of disk space and bandwidth usage. According to the OSM wiki, the full tile-set without pre-rendering is on the order of ~1.7TB. Looking at network stats for a number of the tile servers, specifically the www.openstreetmap.org server, I am getting the following breakdown from the weekly charts: So on average, each data access generates ~6.25 b/s. Per day, that works out to 540k bytes/user - seems low though as each map tile is ~30k and just the default map with the settings they use is going to be ~15 tiles... and then they are going to be zooming, panning, etc. Am I reading these numbers correctly? Can anyone who has rolled their own OSM server confirm these are a good estimate? |
|
You are looking at the wrong stats if you want a tile server. Those stats are just for the website without the tiles. The OSM tileserver is behind a set of 5 reverse proxy servers as a cdn. The stats for the aggregate are at http://munin.openstreetmap.org/openstreetmap/tile.openstreetmap/index.html The stats for the actual backend tile server are at http://munin.openstreetmap.org/openstreetmap/yevaud.openstreetmap/index.html But there is a good chance you won't see anything like the traffic on osm.org. A usefull resource is also http://wiki.openstreetmap.org/wiki/Tile_Disk_Usage |
It isn't clear which ressource you are trying to estimate. Disk space ? Total bandwidth ? Bandwidth per user ? Number of connections ?
Bandwidth/user - we have estimates for the number of users we will have, but trying to figure out how much a typical OSM end-user consumes, thus my calcs above on bytes per user per day.
@apmon Thanks! Understood on the sheer volume, thus why i am trying to break it down to bandwidth per user. This clarification helps though!