Each time a slave connects to the master there is an interaction where jars are transferred to the slave if needed. This is done by looking at the slave's jar cache and comparing the hashes against the master's jars.
The master does not have a shared cache, so it is has to re-calculate the hashes for every slave it deals with. This is done even when no jars need to be transferred (ie. the slave jar cache is already up-to-date).
If there are a lot of ephemeral slaves that come and go then this becomes wasteful for the master.
Ideally the master's cache should be a singleton that can be accessed for interactions with any slave. There is even a TODO in the JarLoaderImpl that talks about this.
Improvement
Minor
akshay_abd
created issue -
akshay_abd
made changes -