[OSM-dev] planet.openstreetmap.org/replication policy

[Darafei "Komяpa" Praliaskouski]

Main pain is traffic and number of connections.
If traffic is roughly the same in all cases, and number of connections is
the same (you're not reconnecting and using one thread) then there's
effectively no difference.
Let the throttling be implemented server-side if it is needed.

пн, 28 нояб. 2016 г. в 16:35, Oliver Tonnhofer <olt at bogosoft.com>:

> Hi,
>
> > On 28.11.2016, at 13:44, Yves <yvecai at gmail.com> wrote:
> >
> > I think you could take daily and hourly diffs first to cope with the
> import and last planet delay.
>
> That would make the implementation much more complex (what is the first
> hourly diff after a complete day?). It would also not reduce the bandwidth
> by much, as it still needs to download the same data. The code also uses
> keep-alive connections during the catch-up phase to reduce the load.
>
> The code is already working and behaves similar to
> --read-replication-interval from osmosis (as far as I unterstand). So I'm
> just asking what is acceptable: 10 requests/s? 100 requests/s?
>
> Regards,
> Oliver
>
> --
> Oliver Tonnhofer  | Omniscale GmbH & Co KG  | https://omniscale.com
> OpenStreetMap WMS and tile services         | https://maps.omniscale.com
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20161128/fd03842f/attachment-0001.html>