When starting up in a container, My webMethods Server uses an optimization mechanism to reduce startup time. The optimization mechanism launches an in-memory instance of the Derby database to bootstrap My webMethods Server, then transfers the data to the production database, avoiding most of the network latency overhead. By default, on-premises My webMethods Server installations do not use optimized start mechanism, but you can switch it on by adding the following JVM property to the custom_wrapper.conf file: