Hello,

I'm in the process to set up a production tile server that can serve multiple styles. I want to know what dedicated server I have to choose and what should be perfect configuration for it

My requirements are:

  1. high usage, maybe max 20-30k users at the same time during spikes
  2. whole world coverage, limiting max zoom to 18 is ok
  3. tiles size is 256*256
  4. updating my db everyday
  5. I'd like to provide at least 3 map styles.

I need your advice on-

  1. No of vCpu required
  2. RAM Size
  3. Swap Partition Size
  4. Do I need a Raid array for tile cache?(If yes what should be an ideal raid level)
  5. SSD Size and No of SSDs required
  6. HDD Size and No of HDDs required
  7. Boot Drive Size and Do I need a SSD Drive as boot drive

Thanks in advance for your help!

asked 25 Jul '18, 19:24

anuranpal's gravatar image

anuranpal
2161115
accept rate: 0%

edited 26 Jul '18, 04:33

Duplicate question deleted.

(26 Jul '18, 10:26) SimonPoole ♦

This is a community help forum. What you seem to be after is not general help, but specific consulting to help you achieve your goals in a specific commercial project. Consider getting commercial advice.

Generally, the server performance has two aspects: How quickly new tiles can be rendered, and how quickly existing tiles can be served from the cache. A tertiary aspect is how quickly you will be able to apply updates.

Rendering speed depends mostly on how fast your database disks are and how well engineered the style is. You cannot work without SSDs, and for a high end server you should consult with your vendor about what setup gives you the lowest latency and fastest random I/O access. A standard server with 64 GB RAM, 4 quad-core CPUs and fast SSDs with the standard OSM Carto style will give you a rendering performance in the general range of 1-5 metatiles per second (64-320 tiles per second). On lower zoom levels this performance will be much worse, and it is not unheard of for certain metatiles on z6 or z7 to take 120 seconds and longer to render, even if fast disks are available.

Tile access speed depends on the speed of the disks that hold your cache. Massive random I/O is not so important here so it is normally ok to use standard disks. Network I/O can become an issue. Your requirements are massive. 30k tiles "at once", let's say within the same 5 second interval, means 6k tiles per second, with an average tile size of 10kb that's 60 MB per second read from disk and a 500 mBit/s link saturated.

You might get to a point here where it could make sense to have one or more caches in front of your tile server, so that the caches, which would be easily scalable, could take the brunt of the high load. But this depends heavily on your usage scenario, and whether people are likely to request the same tiles often.

You will roughly need about 1TB of SSD space for the DB, 300 GB of tile cache per style, 64 GB RAM, 8 CPUs. Boot drive size is really not an issue.

permanent link

answered 26 Jul '18, 21:37

Frederik%20Ramm's gravatar image

Frederik Ramm ♦
67.0k806161040
accept rate: 24%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×246
×138
×8
×6

question asked: 25 Jul '18, 19:24

question was seen: 510 times

last updated: 26 Jul '18, 21:37

powered by OSQA