One thing one has to know: publisher reload does the reload in another way as you can see in the logs, e.g.:
Initializing save (0), Copying permissions to new file (0), Saving C:\Qlikdata\PL\9f8107ef-c5b8-404c-9efb-aec86f3adbe8_Lagerstand_historisch.qvw.tmp (15), Moving temp file to new file (733), Deleting old file (733)
Closing the document.
Closed the QlikView Engine successfully. ProcessID=4116
Initializing (0), Finished (140)
The task "Lagerstand_historisch.qvw" finished successfully
These file operations will cause a certain overhead. When reloading from the client the are no such file manipulations (copying permissions, creating tmp file etc.) . So, if the increase of reload time is only due to these operations, an increase of RAM won't help.