Each discrete call to WSADMIN instantiates a new JVM, which explains part of its slowness. In addition, each call is committed prior to continuing with the next step

– which can cause problems if an error occurs mid-way through a script. A work around is to wrap the whole process in a transaction and roll-back in case of error.