Lambda in general has starting delays for functions that havent been called in a while. You can create a cloud watch trigger to trigger your code to simply exit, poof, delay gone.

Java has starting delays on lambda? Why would this be the case, I would think that it would have a running VM which could be flushed with new code to run.