We only use small amounts of code from some of our dependencies but currently send the whole JAR up to AppEngine and this could have some effect on instance spin-up time. For instance guava is a ~2MB dependency but we use only a tiny fraction of its classes.
Running Proguard would strip down our WAR to only classes that are actually used, and drastically reduce the total size.
We only use small amounts of code from some of our dependencies but currently send the whole JAR up to AppEngine and this could have some effect on instance spin-up time. For instance guava is a ~2MB dependency but we use only a tiny fraction of its classes.
Running Proguard would strip down our WAR to only classes that are actually used, and drastically reduce the total size.