allstarsilikon.blogg.se - Lambda startup time

#LAMBDA STARTUP TIME FULL#

07:31:24.163 INFO 1 - o.s. : FrameworkServlet dispatcherServlet: initialization completed in 3559 ms 07:31:24.026 INFO 1 - s.w.s.m.m.a.RequestMappingHandlerAdapter : Looking for startup date root of context hierarchy 07:31:23.943 INFO 1 - s.w.s.m.m.a.RequestMappingHandlerAdapter : Looking for startup date root of context hierarchy

07:31:23.426 INFO 1 - s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped onto public .ModelAndView .errorHtml(,) 07:31:22.870 INFO 1 - o.s.s.d.d.r.s.DynamoDBRepositoryFactory : Spring Data Version: null 07:31:22.868 INFO 1 - o.s.s.d.d.r.s.DynamoDBRepositoryFactory : Spring Data DynamoDB Version: DEVELOPMENT (DEVELOPMENT) 07:31:20.604 INFO 1 - o.s. : FrameworkServlet dispatcherServlet: initialization started 07:31:20.604 INFO 1 - c.a.s.p.i.servlet.AwsServletContext : Initializing Spring FrameworkServlet dispatcherServlet 07:31:20.602 INFO 1 - o.s.b.w.servlet.ServletRegistrationBean : Servlet dispatcherServlet mapped to 07:31:20.004 INFO 1 - o.s. : Root WebApplicationContext: initialization completed in 2682 ms 07:31:20.003 INFO 1 - c.a.s.p.i.servlet.AwsServletContext : Initializing Spring embedded WebApplicationContext

07:31:19.801 INFO 1 - f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 annotation found and supported for autowiring 07:31:18.462 INFO 1 - o.s.b.f.s.DefaultListableBeanFactory : Overriding bean definition for bean handlerExceptionResolver with a different definition: replacing scope= abstract=false lazyInit=false autowireMode=3 dependenc圜heck=0 autowireCandidate=true primary=false factoryBeanName=. factoryMethodName=handlerExceptionResolver initMethodName=null destroyMethodName=(inferred) defined in class path resource ] with scope= abstract=false lazyInit=false autowireMode=3 dependenc圜heck=0 autowireCandidate=true primary=false factoryBeanName=config factoryMethodName=handlerExceptionResolver initMethodName=null destroyMethodName=(inferred) defined in class path resource ] 07:31:17.325 INFO 1 - ConfigServletWebServerApplicationContext : Refreshing startup date root of context hierarchy 07:31:17.245 INFO 1 - : The following profiles are active: lambda 07:31:17.244 INFO 1 - : Starting Application on with PID 1 (/var/task started by sbx_user1059 in /)

#LAMBDA STARTUP TIME FULL#

Add Spring Data DynamoDB and do some queries: ĭid I have some misconfiguration here or is it a bug? Full log outputĠ7:31:15.131 INFO .internal.LambdaContainerHandler - Starting Lambda Container HandlerĠ7:31:15.485 INFO. - 1 Spring WebApplicationInitializers detected on classpath.

mvn archetype:generate -DgroupId=my.service -DartifactId=my-service -Dversion=1.0-SNAPSHOT \ -DarchetypeGroupId= \ -DarchetypeArtifactId=aws-serverless-springboot-archetype \ -DarchetypeVersion=1.2.

The request is on hold while it boots up three times. I can see, that Spring Boot starts three times in the Cloudwatch Log. The request should be finished within seconds. On each request I can see Spring Boot Process in Cloudwatch. Running simple Spring Boot Backend Service, which Queries DynamoDB via Spring Data DynamoDB.

Implementations: Spring Boot / Spring Data / spring-data-dynamodb.

Framework version: aws-serverless-java-container-spring:1.2.