style95 commented on issue #5526: URL: https://github.com/apache/openwhisk/issues/5526#issuecomment-2594106141
Since he used Ansible to deploy OW, I believe images are already pulled on invoker machines. When it comes to the difference between two subsequent prewarm starts, along with what Brendan shared above, I also observed that each component needs to create a connection to the other as well. That's the reason why I added explicit [warm-up steps](https://github.com/apache/openwhisk/blob/364ace7a7e670815aa0cf8fccb3de081fa3ad1b9/core/invoker/src/main/scala/org/apache/openwhisk/core/invoker/FPCInvokerReactive.scala#L425) when designing the scheduler. The warming stage in each component uses [a non-existent action](https://github.com/apache/openwhisk/blob/364ace7a7e670815aa0cf8fccb3de081fa3ad1b9/common/scala/src/main/scala/org/apache/openwhisk/core/WarmUp.scala#L32), so it is not related to cache, but it does have effect to reduce the initial invocation time. Since there are less number of components with ShardingPoolBalancer, it might have less impact but I believe network connection would make a difference. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
