WebSockets & Real-Time Systems with Spring · 강의

Spring WebSocket 설정 튜닝

높은 처리량과 짧은 지연 시간이 필요한 환경에 맞게 Spring WebSocket 구성을 최적화합니다.

Spring WebSocket 설정 튜닝은(는) CoddyKit의 무료 WebSockets & Real-Time Systems with Spring 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 WebSockets & Real-Time Systems with Spring 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. WebSockets & Real-Time Systems with Spring 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Why Tune WebSockets?

Your real-time applications need to be fast and reliable! Spring WebSockets come with sensible defaults, but for high-traffic or low-latency scenarios, you'll need to fine-tune them.

This lesson will show you how to optimize your Spring WebSocket configurations for peak performance and improved user experience.

Throughput & Latency Goals

When we talk about performance tuning, we often focus on two key metrics:

Throughput: How many messages or operations can your system handle per second? Higher is usually better.
Latency: How long does it take for a message to travel from sender to receiver? Lower is always better.

Optimizing these ensures a smooth and responsive real-time application.

WebSocket Buffer Sizes

Spring's underlying WebSocket container has limits on the size of individual messages. If your application sends or receives very large messages, the defaults might be too restrictive, causing messages to be rejected.

Text Message Buffer: For text-based messages (e.g., JSON strings).
Binary Message Buffer: For binary data (e.g., images, files).

You can increase these limits to accommodate larger payloads.

Example: Setting Buffer Limits

You can configure the maximum text and binary message buffer sizes by defining a ServletServerContainerFactoryBean bean in your configuration. This ensures the underlying WebSocket container can handle larger messages.

import org.springframework.context.annotation.Configuration;
import org.springframework.web.socket.config.annotation.EnableWebSocket;
import org.springframework.web.socket.config.annotation.WebSocketConfigurer;
import org.springframework.web.socket.config.annotation.WebSocketHandlerRegistry;
import org.springframework.web.socket.server.standard.ServletServerContainerFactoryBean;
import org.springframework.context.annotation.Bean;

@Configuration
@EnableWebSocket
public class WebSocketConfig implements WebSocketConfigurer {

    @Override
    public void registerWebSocketHandlers(WebSocketHandlerRegistry registry) {
        // Handlers would be registered here, e.g., registry.addHandler(myHandler(), "/my-websocket");
    }

    @Bean
    public ServletServerContainerFactoryBean createWebSocketContainer() {
        ServletServerContainerFactoryBean container = new ServletServerContainerFactoryBean();
        container.setMaxTextMessageBufferSize(16384); // Double the default (8192)
        container.setMaxBinaryMessageBufferSize(16384); // Double the default
        System.out.println("WebSocket container buffer sizes set to 16KB.");
        return container;
    }

    public static void main(String[] args) {
        // This config class is loaded by Spring Boot, not run directly.
        // We simulate its effect for demonstration.
        System.out.println("To apply these settings, run a Spring Boot app with this config.");
    }
}

STOMP Frame Size Limits

If you're using STOMP over WebSockets for structured messaging, there are additional buffer limits that control the maximum size of STOMP frames. These are distinct from the raw WebSocket buffer sizes.

Send Buffer Limit: Max size for outgoing STOMP frames from the server.
Receive Buffer Limit: Max size for incoming STOMP frames to the server.

These limits are configured on the STOMP endpoint itself.

Example: STOMP Buffer Tuning

You can set STOMP-specific buffer limits directly on the endpoint registry. This ensures that large STOMP messages (which contain headers and body) don't exceed your desired limits, preventing potential memory issues or denial-of-service attacks.

import org.springframework.context.annotation.Configuration;
import org.springframework.messaging.simp.config.MessageBrokerRegistry;
import org.springframework.web.socket.config.annotation.EnableWebSocketMessageBroker;
import org.springframework.web.socket.config.annotation.StompEndpointRegistry;
import org.springframework.web.socket.config.annotation.WebSocketMessageBrokerConfigurer;

@Configuration
@EnableWebSocketMessageBroker
public class StompWebSocketConfig implements WebSocketMessageBrokerConfigurer {

    @Override
    public void configureMessageBroker(MessageBrokerRegistry config) {
        config.enableSimpleBroker("/topic");
        config.setApplicationDestinationPrefixes("/app");
    }

    @Override
    public void registerStompEndpoints(StompEndpointRegistry registry) {
        registry.addEndpoint("/ws")
                .setAllowedOrigins("*")
                .setSendBufferLimit(512 * 1024) // 512KB for outgoing STOMP frames
                .setReceiveBufferLimit(512 * 1024); // 512KB for incoming STOMP frames
        System.out.println("STOMP endpoint buffer limits set to 512KB.");
    }

    public static void main(String[] args) {
        System.out.println("STOMP WebSocket config with buffer limits prepared.");
    }
}

Keeping Connections Alive (Heartbeats)

WebSocket connections can sometimes become 'stale' without activity, especially when passing through network proxies or load balancers. STOMP heartbeats are crucial for maintaining connection health.

They send small 'ping' messages at regular intervals.
This prevents idle connections from being silently closed.
They help detect unresponsive clients or servers quickly.

You configure both the server's send and receive heartbeat intervals.

Example: Setting STOMP Heartbeats

To enable and configure heartbeats, use the setHeartbeatValue method on your message broker configuration. The array represents [server-send-interval, server-receive-interval] in milliseconds.

import org.springframework.context.annotation.Configuration;
import org.springframework.messaging.simp.config.MessageBrokerRegistry;
import org.springframework.web.socket.config.annotation.EnableWebSocketMessageBroker;
import org.springframework.web.socket.config.annotation.StompEndpointRegistry;
import org.springframework.web.socket.config.annotation.WebSocketMessageBrokerConfigurer;

@Configuration
@EnableWebSocketMessageBroker
public class StompHeartbeatConfig implements WebSocketMessageBrokerConfigurer {

    @Override
    public void configureMessageBroker(MessageBrokerRegistry config) {
        config.enableSimpleBroker("/topic")
              .setHeartbeatValue(new long[]{10000, 10000}); // Server sends every 10s, expects client every 10s
        config.setApplicationDestinationPrefixes("/app");
        System.out.println("STOMP broker heartbeat set to 10 seconds.");
    }

    @Override
    public void registerStompEndpoints(StompEndpointRegistry registry) {
        registry.addEndpoint("/ws").setAllowedOrigins("*");
    }

    public static void main(String[] args) {
        System.out.println("STOMP WebSocket config with heartbeat values prepared.");
    }
}

Message Handler Thread Pool

When your Spring server receives STOMP messages, they are processed by a thread pool. By default, Spring provides a basic one, but for high-load applications, you'll gain significant performance by configuring a dedicated ThreadPoolTaskExecutor.

Core Pool Size: The minimum number of threads always running.
Max Pool Size: The maximum number of threads allowed in the pool.
Queue Capacity: How many tasks can wait if all threads are busy.

Properly sizing this executor is vital for handling concurrent messages efficiently.

Example: Custom Task Executor

You can define a custom ThreadPoolTaskExecutor and assign it to the client inbound channel. This gives you fine-grained control over how many concurrent messages your application can process.

import org.springframework.context.annotation.Configuration;
import org.springframework.messaging.simp.config.MessageBrokerRegistry;
import org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor;
import org.springframework.web.socket.config.annotation.EnableWebSocketMessageBroker;
import org.springframework.web.socket.config.annotation.StompEndpointRegistry;
import org.springframework.web.socket.config.annotation.WebSocketMessageBrokerConfigurer;
import org.springframework.context.annotation.Bean;
import org.springframework.messaging.simp.config.ChannelRegistration;

@Configuration
@EnableWebSocketMessageBroker
public class CustomExecutorConfig implements WebSocketMessageBrokerConfigurer {

    @Override
    public void configureMessageBroker(MessageBrokerRegistry config) {
        config.enableSimpleBroker("/topic");
        config.setApplicationDestinationPrefixes("/app");
    }

    @Override
    public void registerStompEndpoints(StompEndpointRegistry registry) {
        registry.addEndpoint("/ws").setAllowedOrigins("*");
    }

    @Override
    public void configureClientInboundChannel(ChannelRegistration registration) {
        registration.taskExecutor(clientInboundExecutor());
        System.out.println("Custom client inbound task executor configured.");
    }

    @Bean
    public ThreadPoolTaskExecutor clientInboundExecutor() {
        ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
        executor.setCorePoolSize(8); // Start with 8 threads
        executor.setMaxPoolSize(16);  // Allow up to 16 threads
        executor.setQueueCapacity(512); // Queue up to 512 tasks
        executor.setThreadNamePrefix("StompInbound-");
        executor.initialize();
        return executor;
    }

    public static void main(String[] args) {
        System.out.println("STOMP WebSocket config with custom task executor prepared.");
    }
}

Quick Check: Tuning Options

Which of the following Spring WebSocket configuration settings can directly impact the performance (throughput and/or latency) of your real-time application?

Recap: Optimize Your WebSockets

Great job! You've learned how to fine-tune your Spring WebSocket applications for better performance.

We adjusted WebSocket buffer sizes for larger messages.
Configured STOMP frame limits for structured data.
Set up heartbeats to maintain connection health.
Customized the message handling thread pool for concurrency.

Applying these settings is crucial for building robust, scalable, and high-performance real-time systems!

자주 묻는 질문

“Spring WebSocket 설정 튜닝” 강의는 무료인가요?

네 — “Spring WebSocket 설정 튜닝” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 WebSockets & Real-Time Systems with Spring 강의 전체를 잠금 해제할 수 있습니다. WebSockets & Real-Time Systems with Spring 강의에는 총 4개의 강의가 포함되어 있습니다.

“Spring WebSocket 설정 튜닝”에서 뭘 배우나요?

높은 처리량과 짧은 지연 시간이 필요한 환경에 맞게 Spring WebSocket 구성을 최적화합니다. 브라우저에서 직접 실행하는 실습 코드로 WebSockets & Real-Time Systems with Spring을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

WebSockets & Real-Time Systems with Spring을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 WebSockets & Real-Time Systems with Spring은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.

“Spring WebSocket 설정 튜닝” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 WebSockets & Real-Time Systems with Spring 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 WebSockets & Real-Time Systems with Spring 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← WebSockets & Real-Time Systems with Spring(으)로 돌아가기