id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
16508	[Performance] Reading object history is inefficient	mmd	Upliner	"Currently, the reverter plugin fetches each object version via a single select.

GET https://api.openstreetmap.org/api/0.6/node/3221532428/1
GET https://api.openstreetmap.org/api/0.6/node/1711424674/1
GET https://api.openstreetmap.org/api/0.6/node/5739339750/1
GET https://api.openstreetmap.org/api/0.6/node/1711397715/1
GET https://api.openstreetmap.org/api/0.6/node/1711397713/1
GET https://api.openstreetmap.org/api/0.6/node/3221532426/2
GET https://api.openstreetmap.org/api/0.6/node/26819461/8
GET https://api.openstreetmap.org/api/0.6/node/1711376838/4
GET https://api.openstreetmap.org/api/0.6/node/1711424666/1 

This is quite inefficient to the fixed cost for each call. Luckily, the OSM API 0.6 offers a multi fetch call (see https://wiki.openstreetmap.org/wiki/API_v0.6#Multi_fetch:_GET_.2Fapi.2F0.6.2F.5Bnodes.7Cways.7Crelations.5D.3F.23parameters)

By using a multi fetch, the call above could be turned into a single call to fetch the respective object version

GET https://api.openstreetmap.org/api/0.6/nodes?nodes=3221532428v1,1711424674v1,5739339750v1,1711397715v1,1711397713v1,3221532426v2,26819461v8,1711376838v4,1711424666v1"	enhancement	closed	normal		Plugin reverter		fixed	performance multi fetch