Community
Participate
Working Groups
The bundle data is cached in the configuration area. In case of remote shared install, accessing it can be costly. First we need to verify that it is actually costly, if so we need to come up with a scheme to fix that. For example we could have a local copy of the file.
If access to the bundledata in the shared install is costly then we have other issues. Would this not mean that access to the binary bundles in the shared install would also be costly? The bundledata is a relatively small file (compared to the rest of the shared binaries) and is only read once at startup. If remote access is slow then we should consider how one would create a local copy of everything from a remote install. Or simply do not suggest remote installs unless your access is fast.
I think that what I meant was .lazydata file.
all the bundles etc might be remove (in the shared install) but if we are repeately going to the cache for stuff and the cache is in some shared spot, there may be some issues. It would be interesting to know if there are options for putting the caches locally.
We do not plan to fix this.