[openstreetmap/openstreetmap-website] Change the way changesets are displayed to use achavi (#1376)

[mmd]

We're making some (albeit slow) progress on large changesets, like www.openstreetmap.org/changeset/45018920 (btw: kudos to @nrenner for supporting this effort!).

As you can see [here](https://github.com/nrenner/achavi/issues/9#issuecomment-315349239), an `(id: ...)` based approach brings response time for the Overpass query down to 4s, a [massive 50k cs](www.openstreetmap.org/changeset/45656403) all over the world cs is at 11s, many other  changesets with a large number of items and/or large extent are at about 1s. 

Now, the main drawback at this time is, that we'd need a list of relevant {node/way/rel} ids, which we retrieve from the main OSM API and later pass to the Overpass query. Of course, it would make more sense to get those ids per changeset directly from Overpass API. That's still a todo for @drolbr, I would assume.

This complements efforts by @geohacker to get decent history visualization, where caching is not yet available for older changesets, like for the initial example of cs 45018920: https://osmcha.mapbox.com/changesets/45018920

So bottom line here is: we have some ideas to speed up things without resorting to additional caching (which doesn't hurt of course :)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1376#issuecomment-315603218
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20170716/ee5b2547/attachment.html>