id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
20510	Default maximum memory setting (-Xmx) for distribution packages	wiktorn	Don-vip	"Currently for our distribution channels we have following maximum heap memory settings:
||= distribution channel =||= maximum memory =||
|| [[https://josm.openstreetmap.de/download/josm.jnlp|josm.jnlp]] || 2048m||
|| [[https://josm.openstreetmap.de/download/windows/josm-setup.exe|Windows Installer]] || 2048m||
|| [[https://josm.openstreetmap.de/download/macosx/josm-macosx.zip|macOS package]] || 8192m||

Two questions:
1. Why for macOS we have 4x more memory than for other platforms?
2. Why do we set this up anyway? As far as I've tested, Java defaults to 25% of physical memory and taking into account current configurations, I'd assume that for 90+% users, this would at least give us the same result or higher. On the other hand, when we have `-Xmx` occupying high percentage  of physical memory, overall performance may be unsatisfying due to high swap usage

For a start, I'd lower the macOS -Xmx to be on par with other platforms.

See: #20443, #20497, #19937"	defect	closed	normal	21.04	Core		fixed	memory jvm performance	stoecker