Milo's point on database growth is actually very important, and I worry that it might be missed. We shouldn’t be concerned about shaving a few bytes off of the tag values to save space, or the power consumption of different processors.
OSM needs a growth plan. We should already have pretty solid metrics on how fast the database is growing, and roughly when we’ll outgrow the current database architecture. I’d be very happy to see OSM grow by 10x, 100x, or more as we continue to map everything the world, and we should be prepared for that. Curious if anyone else is thinking about this? Bryan > On Jan 22, 2018, at 3:57 AM, Milo van der Linden <m...@dogodigi.net> wrote: > > In my personal opinion, the database will grow and keep growing. So > instead of looking at means to make things smaller, I think we should > look at enabling even more storage. Couldn't geographical > "shards/segments" be a solution? Like, keeping a database for Europe, > Asia, North-America and so on that are glued together in a smart way, > but allow for downloading partials straight from the main databases? > And might it be smart to create a more distributed database? When I > look at the hardware, there are currently 3 database; karm, ramoth and > katla and it seems all 3 are in the UK. > > Not intending to start an off topic, but this is just my opinion. > > 2018-01-21 12:05 GMT+01:00 Oleksiy Muzalyev <oleksiy.muzal...@bluewin.ch>: >> On 21.01.18 10:04, Martin Koppenhoefer wrote: >> >> >> On 21. Jan 2018, at 09:21, Oleksiy Muzalyev <oleksiy.muzal...@bluewin.ch> >> wrote: >> >> For example, Intel i7-8700K 3.7 GHz 8th generation processor consumes 95 W >> [2], add to this the fans, hard disks, etc., it comes to 400 W power supply >> unit. .... >> >> For comparison, the Raspeberry Pi 3 single-board computer requires only 10 W >> power supply [4], 40 times less. >> _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
