I started planet rendering yesterday evening for v3.1 mainly to test performance and the modified distributed. And also so we can put it on the CDN to test in the mobile apps.
The performance has increased a lot... right now it rendered half the planet in 12hrs with 6 machines.
With speeds on the workers ranging from 30 tiles/s to 80 tiles/s for each process (4 processes on each server). I guess the savings come from the table functions.

It really did render the planet in 24hrs! 馃巻
But then sadly last night the master restarted on its own and RabbitMQ lost the queues (so I don't know for sure whether all has worked out down to the last 2k z8 tiles).
But the important result of this is the knowledge we can render the planet in <24 hrs and I could fix issues in the distributed components (because they are now separated) and then later on check how well it works with mobile (with CDN).
Upload is taking place, once uploaded it will be this URL: https://openmaptiles-downloads.os.zhdk.cloud.switch.ch/planet_v3.1mbtiles
This is fantastic, it will help significantly with doing live updates too if the performance is solid.
The Planet v3.1 is hosted on the OSM2VectorTiles CDN now, for easier evaluation and testing:
http://osm2vectortiles.tileserver.com/#v3/mapboxgl
I expect we rerender the whole planet later this week - once the schema gets more stable (milestone v3.3), and then I update the CDN again.
Most helpful comment
It really did render the planet in 24hrs! 馃巻
But then sadly last night the master restarted on its own and RabbitMQ lost the queues (so I don't know for sure whether all has worked out down to the last 2k z8 tiles).
But the important result of this is the knowledge we can render the planet in <24 hrs and I could fix issues in the distributed components (because they are now separated) and then later on check how well it works with mobile (with CDN).
Upload is taking place, once uploaded it will be this URL: https://openmaptiles-downloads.os.zhdk.cloud.switch.ch/planet_v3.1mbtiles