Well, I looked through what goes on in those two steps, and I don’t think there is much we can do to speed it up. It’s all a bunch of File IO reading and writing to files in the cache.
The cache analyze step reads through each Jar and calculates a CRC for the jar to see if it needs to donwload a new version. The init working dir copies each jar to an temp dir to actually run off of so that the actual jars can be modified later without worrying about file locks.
Clearly this whole idea was based on the assumption that a user’s local dir is LOCAL to the client’s hard drive, and thus fast. I think we’ll have to have a way for you to put the .ignition folder elsewhere - there’s only so much speed we can eek out of the system when the drive is really located over the network.