We should consider increasing the Java heap size in startup.sh/.bat to avoid OutOfMemory errors during first-time installations. I've downloaded the 5.4 bundle, installed and started the author instance, then started the installation of the public instance. The installation froze, which I diagnosed as a memory problem, though I didn't explicitely get an OutOfMemoryError in the logs.

So, without actually doing anything special, I wasn't able to just download and run the bundle. Instead, I installed and started author, shutdown, started up again, installed and started public, shutdown again, then started the server a second time before I could get going.

This is not a very compelling first-time experience for new customers, especially because most of them won't be able to fix the problem as they don't know the system well enough yet.

In our release notes for 5.4, we actually advice to increase the heap size to users of eebundle might run into Out of Memory errors: https://documentation.magnolia-cms.com/display/DOCS/Release+notes+for+Magnolia+5.4#ReleasenotesforMagnolia5.4-Knownissues