id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
4554	Fixing duplicate nodes takes increasingly longer when more nodes are being fixed simultaneously	fsteggink	team	"After running the validator, the larger the number of duplicate nodes one wants to fix simultaneously, the more time it takes. The time is even more for each individual node. I guess that the performance degradation is at least quadratic, possibly more. I find that odd, since the detection of duplicate nodes itself is much quicker, and there are much more nodes to test.

So, I'm currently fixing duplicate nodes on smaller sets, by selecting only a part of the duplicate nodes. (Run validator without selection, select duplicate nodes, unselect portion of it, run validator again, fix.) This is faster, but quite annoying to do, especially when there are thousands of nodes to be fixed.

JOSM version: 2971"	defect	closed	normal		Core validator	latest	fixed	duplicate nodes fix