July 11, 2022:\n\nMore information from Actian Engineering Team:\n\nThe main factors that could influence the download performance during Loadnrun are\n\t? network speed\n\t? size of downloaded files (images, config files, etc.)\n\t? contention when several downloads are due to be executed at the same time\n\nA contention could happen if multiple users perform a download at the same time as:\n\t? The Loadnrun server is run as OpenROAD server application (oraso process on the server).\n\t? Only one remote procedure call is served at a time for each oraso process -downloading via Loadnrun is using remote procedure calls\n\t? The default configuration for the Loadnrun server uses one slave process (means one oraso process),\n\t? therefore it would only allow to process one download at a time (all others are queued, so they will wait).\n\nThe default configuration for the ?Loadnrun? server application can be amended to provide parallel downloads by the following changes in VOSA (or in the orserver.json configuration file):\n\t? Increase the number in the ?Max. Slaves? option (maxslaves member in \t  orserver.json)\n\t? Change the ?-L? flag within the ?Flags? setting (cmdflags member in \t  orserver.json) to include the Slave ID:\n\t? from <em>-Lloadnrun.log</em> to <em>-Lloadnrun_%s.log</em>\n\t? This is done in order to prevent conflicts when different processes write to the same log file.\n\nThis will (after an OpenROAD Server restart) allow to run multiple downloads in parallel by using multiple oraso processes (up to the configured number).