Oh yeah, that makes perfect sense then. The bootstrap launcher uses a folder called “.ignition” under the user’s home directory (usually something like “C:\Users\Jonathan” on Windows 7) to store the jar file cache. It downloads compressed jar files in pack200 format, writes those to disk, and then decompresses them, and writes the full jar file to disk as well.
Of course, if your user directory isn’t on the local disk, you’re going to be doing a bunch of network IO, which is what has to be taking the time.
I think we have two options going forward, but both will require us to make a change to the software. One is for us to investigate - there may be some IO buffering we can do to minimize the write calls. I’m assuming you’ve got reasonably fast network (gigabit?), in which case I wouldn’t expect to see a slowdown of the magnitude you’re describing.
If that fails, we’d have to add some option to be able to optionally specify an alternate cache directory.
Question (maybe for your IT dept): would it be difficult to place a file in every one’s home dir? Perhaps the client could look for a file called “.ignition-client.prefs” or something that, if it is present, could point to an alternate cache dir. That way the setting could be set on a per-machine basis which might be desirable, as opposed to a global setting that affects all clients. (It would be tough to specify a good alternate location that would work on both linux clients vs windows clients for example).