Spring Boot 容器选择 Undertow 而不是 Tomcat

最新推荐文章于 2024-02-19 21:20:09 发布
最新推荐文章于 2024-02-19 21:20:09 发布
阅读量1.2k 收藏 1
点赞数
文章标签： java 网络 开发工具

Spring Boot 内嵌容器Undertow参数设置

配置项：

# 设置IO线程数, 它主要执行非阻塞的任务,它们会负责多个连接, 默认设置每个CPU核心一个线程
# 不要设置过大，如果过大，启动项目会报错：打开文件数过多
server.undertow.io-threads=16

# 阻塞任务线程池, 当执行类似servlet请求阻塞IO操作, undertow会从这个线程池中取得线程
# 它的值设置取决于系统线程执行任务的阻塞系数，默认值是IO线程数*8
server.undertow.worker-threads=256

# 以下的配置会影响buffer,这些buffer会用于服务器连接的IO操作,有点类似netty的池化内存管理
# 每块buffer的空间大小,越小的空间被利用越充分，不要设置太大，以免影响其他应用，合适即可
server.undertow.buffer-size=1024

# 每个区分配的buffer数量 , 所以pool的大小是buffer-size * buffers-per-region
server.undertow.buffers-per-region=1024

# 是否分配的直接内存(NIO直接分配的堆外内存)
server.undertow.direct-buffers=true

来看看源代码：

https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io/undertow/Undertow.java

ioThreads = Math.max(Runtime.getRuntime().availableProcessors(), 2);

workerThreads = ioThreads * 8;

//smaller than 64mb of ram we use 512b buffers
if (maxMemory < 64 * 1024 * 1024) {
    //use 512b buffers
    directBuffers = false;
    bufferSize = 512;
} else if (maxMemory < 128 * 1024 * 1024) {
    //use 1k buffers
    directBuffers = true;
    bufferSize = 1024;
} else {
    //use 16k buffers for best performance
    //as 16k is generally the max amount of data that can be sent in a single write() call
    directBuffers = true;
    bufferSize = 1024 * 16 - 20; //the 20 is to allow some space for protocol headers, see UNDERTOW-1209
}

很显然，Undertow认为它的运用场景是在IO密集型的系统应用中，并且认为多核机器是一个比较容易满足的点，Undertow初始化假想应用的阻塞系数在0.8~0.9之间，所以阻塞线程数直接乘了个8，当然，如果对应用较精确的估测阻塞系数，可以配置上去。

 

Spring Boot内嵌容器支持Tomcat、Jetty、Undertow。为什么选择Undertow？

这里有一篇文章，时间 2017年1月26日发布的：
Tomcat vs. Jetty vs. Undertow: Comparison of Spring Boot Embedded Servlet Containers

1. Setup Spring Boot Application

We will use Maven to setup a new project in Eclipse with the appropriate dependencies. We will use the starter parent for this example but the dependencies in a production application will likely be altered to streamline, optimize or customize.

1.1 Setup Spring Boot Dependencies

The default embedded servlet container is Tomcat. This version of Spring Web 1.4.3 brings in Tomcat version 8.5.6.

pom.xml

<parent>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-starter-parent</artifactId>
   <version>1.4.3.RELEASE</version>
</parent>
 
<dependencies>
   <!-- TOMCAT -->
   <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-web</artifactId>
   </dependency>
</dependencies>

1.2 Setup Spring Boot Main Application and Controllers

To setup the Spring Boot application you include the @SpringBootApplication annotation in your Main class. The @SpringBootApplication annotation brings in @SpringBootConfiguration, @EnableAutoConfiguration and @ComponentScanannotations.

Application.java

@SpringBootApplication
@ConfigurationProperties
public class Application {
public static void main(String[] args) {
   SpringApplication.run(Application.class, args);
}

You may choose to eliminate this annotation and add the @SpringBootConfiguration alone or to another class that allows you to customize the configuration. The @ComponentScan will scan your application for items like the @Controller you will need to setup a RESTful service. The following controller will return a simple “Hello World” string from a HTTP GET request. We have also included in the bundled example another endpoint mapping that returns a complex object type.

SampleController.java

@Controller
public class SampleController {

@Autowired
private ResourceLoader resourceLoader;

@RequestMapping("/")
@ResponseBody
public String home() {
   return "Hello World!";
}

1.3 Key Configuration Parameters

The default properties for all the embedded servlet containers are the same. Some of the most important properties to consider are the properties for configuring startup information like ports and application name, TSL, access logs, compression and many more.

For example, to configure SSL add the following to key value pairs to the application.properties.

application.properties

server.port=8443
server.ssl.key-store=classpath:keystore.jks
server.ssl.key-store-password=secret
server.ssl.key-password=another-secret

1.4 How to Find Additional Parameters

To explore the parameters for Spring boot applications you can add the Spring actuator dependency and the @ConfigurationProperties annotation to your Main class. You then visit the /configprops endpoint on your application to get a list of the available properties.

Application.java

@SpringBootApplication
@ConfigurationProperties
public class Application {

pom.xml

<dependency>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-starter-actuator</artifactId>
</dependency>

http://localhost:8080/jcg/service/configprops

1.5 Change version of Embedded Servlet Containers

The embedded servlet container versions are defined in the following parent dependency from the pom. You can change the version of the embedded servlet container by explicitly including the dependency and identifying a new version in the pom. We will show you how in the examples below.

pom.xml

<dependency>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-dependencies</artifactId>
   <version>1.3.7.RELEASE</version>
</dependency>

2. Tomcat

As Tomcat is the default embedded servlet container there is nothing you need to do to the default implementation to use Tomcat. You can change the version of Tomcat you are using or change properties in the pom.xml or application.properties files.

2.2 Change Version of Tomcat

pom.xml

<properties>
   <tomcat.version>8.5.6</tomcat.version></properties>
<dependency>
   <groupId>org.apache.tomcat.embed</groupId>
   <artifactId>tomcat-embed-core</artifactId>
   <version>${tomcat.version}</version>
</dependency>
<dependency>
   <groupId>org.apache.tomcat.embed</groupId>
   <artifactId>tomcat-embed-el</artifactId>
   <version>${tomcat.version}</version>
</dependency>
<dependency>
   <groupId>org.apache.tomcat.embed</groupId>
   <artifactId>tomcat-embed-websocket</artifactId>
   <version>${tomcat.version}</version>
</dependency>

3. Jetty

To change the embedded servlet container to Jetty you need to edit the pom file to remove the Tomcat dependency and add Jetty.

3.1 Change to Jetty (version 9.3.14)

pom.xml

<dependency>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-starter-web</artifactId>
   <exclusions>
      <exclusion>
         <groupId>org.springframework.boot</groupId>
         <artifactId>spring-boot-starter-tomcat</artifactId>
      </exclusion>
   </exclusions>
</dependency>
<dependency>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-starter-jetty</artifactId>
</dependency>

4. Undertow

To change the embedded servlet container to Undertow you need to edit the pom file to remove the Tomcat dependency and add Undertow.

4.1 Change to Undertow (version 1.3.24 final)

Notice the undertow version included in the spring boot starter is incorrect, referring to 1.3.25. You’ll need to change it to 1.3.24.Final for this to work at the time of this article.

pom.xml

<dependency>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-starter-web</artifactId>
   <exclusions>
      <exclusion>
         <groupId>org.springframework.boot</groupId>
         <artifactId>spring-boot-starter-tomcat</artifactId>
      </exclusion>
   </exclusions>
</dependency>
<dependency>
   <groupId>org.springframework.boot</groupId>
   <artifactId>spring-boot-starter-undertow</artifactId>
</dependency>
<dependency>
   <groupId>io.undertow</groupId>
   <artifactId>undertow-core</artifactId>
   <version>1.3.24.Final</version>
</dependency>
<dependency>
   <groupId>io.undertow</groupId>
   <artifactId>undertow-servlet</artifactId>
   <version>1.3.24.Final</version>
</dependency>

5. Performance and Load

In this example, we will analyze both the peformance of HTTP requests and the memory footprint at startup of all three embedded servlet containers. We used JMeter to measure performance by simulating load and JVisualVM to look at the memory footprint.

5.1 Measure Performance

In this example, we will analyze both the peformance of simple RESTFul GET requests that return a string and more complex GET requests that return complex JSON objects. JMeter is the tool used to measure the performance of the the three different types of containers. The key to setting up this test was establishing thread groups with the appropriate load, a counter to dynamically update the input to the API and report viewers to display or aggregate the results. For the simple string examples, we used a thread group with 1000 threads that would loop 3 times through the sequence. It also used a ramp up time of 10 seconds. For the complex object examples, we used the same parameters but did not loop.

JMeter Tomcat Thread Group

JMeter Tomcat Summary Report

5.1.1 Tomcat
5.1.1.1 Simple String
Label# SamplesAverageMinMaxStd. Dev.Error %ThroughputReceived KB/secSent KB/secAvg. Bytes
Startup30007154935.783743610293.858360355.9593557255.67238466195
Others300010451.3596616820287.880241854.8209444954.53981144195
Others300010241.1550322750292.112950355.6269778555.3417113195
5.1.1.2 Complex Object with Dynamic Data
Label# SamplesAverageMinMaxStd. Dev.Error %ThroughputReceived KB/secSent KB/secAvg. Bytes
Startup100011431601322.8671905097.68486861202.333599919.937634322121
Others100032171.328216473097.88566954202.749516719.97861812121
Others100021161.110529603098.52216749204.067887920.108528332121
Others100021211.344498419098.53187506204.087995120.110509662121
5.1.2 Jetty
5.1.2.1 Simple Object
Label# SamplesAverageMinMaxStd. Dev.Error %ThroughputReceived KB/secSent KB/secAvg. Bytes
Startup30007056140.137050650291.516859456.082833355.22878197
Others300010211.0589250310293.599530256.4835033855.6233485197
Others300010210.9260343170294.348508656.6275939555.7652448197
5.1.2.2 Complex Object with Dynamic Data
Label# SamplesAverageMinMaxStd. Dev.Error %ThroughputReceived KB/secSent KB/secAvg. Bytes
Startup100011031397278.7961107098.13542689203.362671719.933758592122
Others100032201.500210319098.48335631204.083673920.004431752122
Others100032452.729377218098.29942003203.702509119.967069692122
5.1.3 Undertow
5.1.3.1 Simple Object
Label# SamplesAverageMinMaxStd. Dev.Error %ThroughputReceived KB/secSent KB/secAvg. Bytes
Startup30006045131.61887020295.683027863.8144034656.01807363221
Others300010221.2554478620292.740046863.1792483955.46051669221
Others300010181.5594779750294.377391863.5326206955.77071681221
5.1.3.2 Complex Object with Dynamic Data
Label# SamplesAverageMinMaxStd. Dev.Error %ThroughputReceived KB/secSent KB/secAvg. Bytes
Startup10007031114197.1333241097.059109203.396936119.620442012145.893
Startup1000423852132.6443576098.02960494205.632413520.007995542148
Others100032191.293570253098.55129595206.630500420.018231992147
Others100022271.659250132098.74592673207.038578820.057766372147
Others100021171.260904041098.28975821206.082139519.965107142147

 

5.2 Measure Memory

To measure the memory of each embedded servlet container we looked at the memory usage on startup. JVisualVM is a tool provided with the Java Development Kit for visualizing the memory and footprint of java applications. We used this tool to show the initial startup impact of each of the three embedded servlet containers. The heap size and thread counts are key in analyzing this initial footprint. The ten threads that are common to all three containers include: JMX server connection timeout, RMI Scheduler, RMI TCP Connection (2), RMI TCP Accept, Attach Listener, DestroyJavaVM, Signal Dispatcher, Finalizer and Reference Handler.

JVisualVM Report

5.2.2 Tomcat

Heap Size: 697,827,328 B
Used: 124,260,976 B
Max: 2,147,483,648 B

Threads: 17 Live, 22 Started

5.2.3 Jetty

Heap Size: 628,621,312 B
Used: 311,476,776 B
Max: 2,147,483,648 B

Threads: 19 Live, 22 Started

5.2.4 Undertow

Heap Size: 630,718,464 B
Used: 114,599,536 B
Max: 2,147,483,648 B

Threads: 17 Live, 20 Started

6. 对比

6.1 性能

压测结果：从上面的6张压力测试报告中，可以看到3个容器在相同的用例及并发请求下，Undertow稍微比Tomcat和Jetty好一点。

资源消耗：JETY启动时内存占用最大，使用311 MB。Tomcat和Undertow的初始脚印相似，在120 MB左右，Undertow出现在114 MB的最低水平。响应头中的关键差异在于默认情况下默认情况下包括HTTP持久连接。该头将在支持持久连接的客户端中使用，以通过重用连接细节来优化性能。

6.1.1 Tomcat Response Headers
Content-Type →application/json;charset=UTF-8
Date →Mon, 09 Jan 2017 02:23:26 GMT
Transfer-Encoding →chunked
X-Application-Context →JcgSpringBootContainers:# Application index.
6.1.2 Jetty Response Headers
Content-Type →application/json;charset=UTF-8
Date →Mon, 09 Jan 2017 02:29:21 GMT
Transfer-Encoding →chunked
X-Application-Context →JcgSpringBootContainers:# Application index.

 

6.1.3 Undertow Response Headers
Connection →keep-alive
Content-Type →application/json;charset=UTF-8
Date →Mon, 09 Jan 2017 02:20:25 GMT
Transfer-Encoding →chunked
X-Application-Context →JcgSpringBootContainers:# Application index.

7. 结论

这些数字表明Undertow在性能和内存使用方面是最好的。令人鼓舞的是，Undertow 正在接受最新的能力，并默认为持久的连接。这些数字并不表示在这个例子中使用的负载有显著的性能差异，但我想它们会缩放，如果性能是最重要的因素，则Undertow 是应用程序的正确匹配。认为一个组织可能因为熟悉它的能力而喜欢嵌入的servlet容器也是合理的。很多时候默认设置将不得不改变，因为应用程序要求包括性能、内存使用和功能。

=========================分割线=================================================================================

在Spring Boot中使用 Undertow 而不是 Tomcat

1、Maven示例：

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-web</artifactId>
    <exclusions>
        <exclusion>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-tomcat</artifactId>
        </exclusion>
    </exclusions>
</dependency>
<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-undertow</artifactId>
</dependency>

2、配置Undertow，application.yml示例：

server.undertow.accesslog.dir= # Undertow access log directory.
server.undertow.accesslog.enabled=false # Enable access log.
server.undertow.accesslog.pattern=common # Format pattern for access logs.
server.undertow.accesslog.prefix=access_log. # Log file name prefix.
server.undertow.accesslog.rotate=true # Enable access log rotation.
server.undertow.accesslog.suffix=log # Log file name suffix.
server.undertow.buffer-size= # Size of each buffer in bytes.
server.undertow.buffers-per-region= # Number of buffer per region.
server.undertow.direct-buffers= # Allocate buffers outside the Java heap.
server.undertow.io-threads= # Number of I/O threads to create for the worker.
server.undertow.max-http-post-size=0 # Maximum size in bytes of the HTTP post content.
server.undertow.worker-threads= # Number of worker threads.

3、使用 Undertow 监听多个端口示例：

@Bean
public UndertowEmbeddedServletContainerFactory embeddedServletContainerFactory() {
    UndertowEmbeddedServletContainerFactory factory = new UndertowEmbeddedServletContainerFactory();
    factory.addBuilderCustomizers(new UndertowBuilderCustomizer() {

        @Override
        public void customize(Builder builder) {
            builder.addHttpListener(8080, "0.0.0.0");
        }

    });
    return factory;
}

 



weixin_33713503
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
sprintboot项目undertow替换tomcat方法
05-06
sprintboot项目undertow替换tomcat方法，详细介绍了springboot项目如何把tomcat服务替换成性能更优的undertow服务
SpingBoot之替换容器为Undertow
jcc4261的博客
11-14 1375
Undertow 是一个采用 Java 开发的灵活的高性能Web服务器，提供包括阻塞和基于NIO的非堵塞机制。Undertow 是红帽公司的开源产品，是 Wildfly 默认的 Web 服务器。Undertow 提供一个基础的架构用来构建 Web 服务器，这是一个完全为嵌入式设计的项目，提供易用的构建器 API，完全向下兼容和低级非堵塞的处理器。
undertow服务线程过多问题排查
csdn_tiger1993的博客
10-24 5814
应用服务使用的是docker容器创建的linux环境，在这个环境下，如果使用Java SE 8u131 (JRE 1.8.0_131-b11)以下的版本，通过Runtime.getRuntime().availableProcessors()，获取cpu核数的使用，取到的是宿主机的核数；XNIO task 线程：默认情况下该类线程对应的线程池初始化所依赖的核心线程数和最大线程数是一致的，都是XNIO-1 I/O线程数的8倍；应用系统1300+多个线程，而且线程不会销毁，达到了1300个线程的告警阈值；
spring boot配置Undertow服务器
m0_72167535的博客
02-19 693
spring boot配置Undertow服务器
undertow配置
zhangjunli的博客
09-22 6130
# 设置IO线程数, 它主要执行非阻塞的任务,它们会负责多个连接, 默认设置每个CPU核心一个线程 # 不要设置过大，如果过大，启动项目会报错：打开文件数过多 #server.undertow.io-threads=32 # 阻塞任务线程池, 当执行类似servlet请求阻塞IO操作, undertow会从这个线程池中取得线程 # 它的值设置取决于系统线程执行任务的阻塞系数，默认值是IO线程数*8 #server.undertow.worker-threads=2000 # 以下的配置会影响buffer,.
UnderTow 核心配置
z69183787的专栏
02-14 6397
本系列代码地址：https://github.com/HashZhang/spring-cloud-scaffold/tree/master/spring-cloud-iiford对于 bufferSize，最好和你系统的 TCP Socket Buffer 配置一样。
undertow配置优化
z69183787的专栏
02-14 2655
因此，从实际情况来看，一定不要采用undertow的官方默认配置。当然啦，官方也是建议工作线程数的配置，取决于你机器的负载情况，其实也就是跟你的具体业务有关，我们现在的业务场景，64线程跑满的情况，CPU利用率仅仅百分之十几、CPU内存远远没利用完，再有请求过来，undertow则直接阻塞队列中，无法正常处理，资源浪费严重，还导致了服务中断的情况。IO线程数, 它主要执行非阻塞的任务，它们会负责多个连接，默认设置每个CPU核心一个线程，不可设置过大，否则启动项目会报错：打开文件数过多。
spring-boot-starter-purge-accesslog:Spring Boot应用程序的AccessLog清除策略
04-30
用于Spring Boot应用程序的可清除AccessLog 为基于Spring Boot的应用程序启用访问日志文件清除功能的模块。 添加项目Lombok代理 该项目使用生成getter和setter等。从命令行编译应该不会引起任何问题，但是在IDE中，...
Spring Boot 2.0培训.pdf
11-20
创建独立的Spring 应用程序；...形式运行Spring Boot 的项目，而无须其他服务器配置：对于配置， Spring Boot 提供Spring 框架的最 大自动化配置，大量使用自动配置，使得开发者对Spring 的配置尽量减少：此
logback-access-spring-boot-starter：用于Logback访问的Spring Boot Starter
01-30
logback-access-spring-boot-starter 用于 Starter。 注意：此页面用于Spring 。... Java 8 Spring Boot 2.0.0 嵌入式Tomcat 8.5.28 嵌入式码头9.4.8 嵌入式Undertow 1.4.22 登录后访问1.2.3用法添加依赖“ logba
基于Spring Boot框架的员工管理系统的设计与实现-初始框架.zip
最新发布
04-24
springboot框架 一、Spring Boot基础应用 Spring Boot特征 ...4.使部署变得简单，SpringBoot内置了三种Servlet容器，Tomcat，Jetty,undertow.我们只需要一个Java的运行环境就可以跑SpringBoot的项目了
Spring Boot 内嵌容器Undertow参数设置
热门推荐
Lovnx
12-26 3万+
配置项：# 设置IO线程数, 它主要执行非阻塞的任务,它们会负责多个连接, 默认设置每个CPU核心一个线程，不要设置过大，如果过大，启动项目会报错：打开文件数过多server.undertow.io-threads=16# 阻塞任务线程池, 当执行类似servlet请求阻塞操作, undertow会从这个线程池中取得线程,它的值设置取决于系统的负载，高吞吐量的应用可以设置大一点server.unde
Spring(21) 在 Spring Boot 中使用 Undertow 作为嵌入式服务器
ACGkaka的博客
01-25 1727
Spring(21) 在 Spring Boot 中使用 Undertow 作为嵌入式服务器
SpringCloud常用配置总结（转）
小南
11-08 1656
原作者未知，但很佩服这种收集的能力。 server server.address 指定server绑定的地址 server.compression.enabled 是否开启压缩，默认为false. server.compression.excluded-user-agents 指定不压缩的user-agent，多个以逗号分隔，默认值为:text/html,text/xml,text/...
spring boot内嵌undertow配置一定要优化
mojolang
08-11 4506
undertow默认配置情况下，官方默认配置的是 CPU核数*8，比如8核CPU，实际工作线程数也就8*8=64，这个配置对于高并发场景来看，一台8核CPU的机器一般内存都会32G或以上，即使跑满64线程，占用的资源远远无法充分利用该机器的性能。......
spring 测试demo乱码_关于SpringBoot项目使用undertow容器的中文参数乱码问题的真正解决方案...
weixin_28979339的博客
12-24 995
实验项目 SpringBoot 版本为 2.3.5.RELEASE如若担心其他版本是否适用本方案，请查看文章 兼容性 章节一、概述来到这里的朋友，你一定遇见了中文参数乱码的问题。你是否有以下症状：项目已设置了 server.servlet.encoding.charset=utf-8 、server.servlet.encoding.force=true 还是会有乱码项目在上条配置的基础上加上了 ...
zuul 参数调优
xiaomin1991222的专栏
08-11 633
适用版本： spring-boot: 1.4.x.RELEASE spring-cloud：Camden.SR3 Hystrix: 1.5.6 spring-boot-tomcat 优化参数： 主要只有2个，最大和最小worker线程： server.tomcat.max-threads=128 # Maximum amount of worker threads. serv...
SpringBoot2服务器属性配置详解-Server、SSL、Servlet、Tomcat、undertow、jetty
chongcuoshen6607的博客
06-27 1534
server server.address= # 定义一个服务器将监听的IP地址 Network address to which the server should bind. server.compression.enabled=false # Whether response co...
spring boot内嵌servlet容器吗
06-03
Spring Boot支持的Servlet容器包括Tomcat、Jetty和Undertow等，可以根据需要选择使用哪一个容器。在应用程序启动时，Spring Boot会自动将所选的Servlet容器嵌入到应用程序中，并为应用程序提供运行环境和资源。同时...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值