Build Native 对于 AWS Lambda 来说太慢了

Question

我从quarkus开始，我的构建原生太慢了(超过一个小时，并且得到了OutOfMemoryError(。我从pom中删除了quarkus<artifactId>quarkus-amazon-lambda</artifactId>依赖项.xml本机构建大约需要13分钟，但没有创建函数.zip文件。

有谁知道为什么这种依赖会导致这种缓慢构建？

夸库斯λ教程： https://quarkus.io/guides/amazon-lambda

我的配置：

• iMac 2011 - i5 2.4Ghz - 16Gb 内存 - 无固态硬盘
• GraalVM CE 19.3.1
• 爪哇 8
• Maven 3.6.3
• 码头工人引擎内存集 10Gb

构建命令

mvn clean install -Pnative -Dnative-image.docker-build=true -Dquarkus.native.enable-jni=true

<?xml version="1.0"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>
<groupId>br.com.fwborges.alexa</groupId>
<artifactId>skill-bus-locator</artifactId>
<version>1.0</version>
<properties>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<surefire-plugin.version>2.22.0</surefire-plugin.version>
<maven.compiler.parameters>true</maven.compiler.parameters>
<quarkus.version>1.5.1.Final</quarkus.version>
<compiler-plugin.version>3.8.1</compiler-plugin.version>
<maven.compiler.source>1.8</maven.compiler.source>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.target>1.8</maven.compiler.target>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-bom</artifactId>
<version>${quarkus.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<!-- AWS Lambda -->
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-amazon-lambda</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-test-amazon-lambda</artifactId>
<scope>test</scope>
</dependency>
<!-- Test -->
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-junit5</artifactId>
<scope>test</scope>
</dependency>
<!-- Database -->
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-hibernate-orm</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-hibernate-validator</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-hibernate-orm-panache</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-jdbc-mysql</artifactId>
</dependency>
<!-- Log -->
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
<version>2.13.1</version>
</dependency>
<!-- Http Clients -->
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-undertow</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-rest-client</artifactId>
</dependency>
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-resteasy-jsonb</artifactId>
</dependency>
<!-- Utils -->
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-text</artifactId>
<version>1.8</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-collections4</artifactId>
<version>4.1</version>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.10</version>
<scope>provided</scope>
</dependency>
<!-- AWS Alexa SDK -->
<dependency>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-amazon-alexa</artifactId>
</dependency>
<dependency>
<groupId>com.amazon.alexa</groupId>
<artifactId>ask-sdk</artifactId>
<version>2.29.0</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-maven-plugin</artifactId>
<version>${quarkus.version}</version>
<executions>
<execution>
<goals>
<goal>build</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.1</version>
</plugin>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>${surefire-plugin.version}</version>
<configuration>
<systemPropertyVariables>
<java.util.logging.manager>org.jboss.logmanager.LogManager</java.util.logging.manager>
</systemPropertyVariables>
</configuration>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>native</id>
<activation>
<property>
<name>native</name>
</property>
</activation>
<build>
<plugins>
<plugin>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-maven-plugin</artifactId>
<version>${quarkus.version}</version>
<executions>
<execution>
<goals>
<goal>native-image</goal>
</goals>
<configuration>
<enableHttpUrlHandler>true</enableHttpUrlHandler>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>

构建日志：

[skill-bus-locator-lambda-1.0-runner:25]    classlist:  44,330.01 ms
[skill-bus-locator-lambda-1.0-runner:25]        (cap):   3,911.88 ms
[skill-bus-locator-lambda-1.0-runner:25]        setup:   9,214.88 ms
18:30:44,765 INFO  [org.hib.val.int.uti.Version] HV000001: Hibernate Validator 6.1.5.Final
18:30:45,188 INFO  [org.hib.Version] HHH000412: Hibernate ORM core version 5.4.16.Final
18:30:45,215 INFO  [org.hib.ann.com.Version] HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
18:30:45,322 INFO  [org.hib.dia.Dialect] HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
18:36:15,233 INFO  [org.jbo.threads] JBoss Threads version 3.1.1.Final
Exception in thread "native-image pid watcher" java.lang.OutOfMemoryError: Java heap space
[skill-bus-locator-lambda-1.0-runner:25]     analysis: 4,862,370.37 ms
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "mysql-cj-abandoned-connection-cleanup"

谢谢！！

Answer 1

我不是AWS Lambdas ans Quarkus的专家。但是，多年来我一直致力于调整基于 Java 的应用程序服务器，并且我已经在您的日志文件中看到了这一点。

18:36:15,233 INFO  [org.jbo.threads] JBoss Threads version 3.1.1.Final
Exception in thread "native-image pid watcher" java.lang.OutOfMemoryError: Java heap 
space

因此，看起来部署过程导致了内存不足 (OOM( 问题，这对于缓慢是有意义的，因为在收到 OOM 错误之前，垃圾回收器已经花费了几个 CPU 周期来尽最大努力清理堆。

因此，应用程序可能存在内存泄漏错误或堆未正确配置。