


Under SpringBoot multi-data source configuration, what is the reason why database access is slow during the day and fast during the night?
Apr 19, 2025 pm 04:06 PMTroubleshooting database performance issues under SpringBoot multi-data source configuration
This article analyzes a case where Atomikos multi-data source configuration is used in SpringBoot projects that lead to database access performance problems. The project connects to three databases (base1, base2, base3), and the base3 database access speed is extremely slow during the day and even timed out, but it returns to normal at night. Base1 and base2 databases always maintain normal access speed. The configuration, data structure and interface of the three databases are completely consistent and are only used to distinguish data from different regions. The project is a real-time large-screen kanban, which frequently requests and switches data sources.
Problem Description: The base3 database (presumably 9771db) has an intermittent delay during the day, with two accesses being about one minute apart, while the night access is normal. This is not a simple connection pool resource exhaustion problem, as resource exhaustion results in continuous performance degradation rather than intermittent delays.
Atomikos data source configuration:
<bean abstract="true" class="com.atomikos.jdbc.AtomikosDataSourceBean" destroy-method="close" id="dataSourceConfig" init-method="init"> <property name="xaDataSourceClassName" value="com.mysql.jdbc.jdbc2.optional.MysqlXADataSource"></property> <property name="poolSize" value="10"></property> <property name="maxPoolSize" value="20"></property> <property name="minPoolSize" value="5"></property> <property name="maxIdleTime" value="5"></property> <property name="maxLifetime" value="60"></property> <property name="borrowConnectionTimeout" value="60"></property> <property name="testQuery" value="SELECT 'x' from dual"></property> <property name="isLoad" value="${datasource.loadDB.haier}"></property> </bean>
This configuration uses the Atomikos connection pool and sets the connection pool size, maximum number of connections, minimum number of connections, maximum idle time, maximum life cycle, connection timeout time and test query statements.
Problem analysis: The problem of intermittent delay during the day is not a simple connection pool configuration or insufficient resources. More detailed runtime data is needed to determine the root cause of the problem, such as network latency, database load, or application code issues.
Solution: It is recommended to use AOP sectional programming to record the detailed information of each database access request, including: data source name, access start time, end time, interface path, etc. By analyzing these data, performance bottlenecks can be accurately positioned and whether delays occur in the network layer, database layer, or application layer code. This will help identify whether the database is overloaded (surge in daytime visits), network connectivity issues (daily network congestion), or application code logic issues.
The above is the detailed content of Under SpringBoot multi-data source configuration, what is the reason why database access is slow during the day and fast during the night?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The difference between HashMap and Hashtable is mainly reflected in thread safety, null value support and performance. 1. In terms of thread safety, Hashtable is thread-safe, and its methods are mostly synchronous methods, while HashMap does not perform synchronization processing, which is not thread-safe; 2. In terms of null value support, HashMap allows one null key and multiple null values, while Hashtable does not allow null keys or values, otherwise a NullPointerException will be thrown; 3. In terms of performance, HashMap is more efficient because there is no synchronization mechanism, and Hashtable has a low locking performance for each operation. It is recommended to use ConcurrentHashMap instead.

StaticmethodsininterfaceswereintroducedinJava8toallowutilityfunctionswithintheinterfaceitself.BeforeJava8,suchfunctionsrequiredseparatehelperclasses,leadingtodisorganizedcode.Now,staticmethodsprovidethreekeybenefits:1)theyenableutilitymethodsdirectly

The JIT compiler optimizes code through four methods: method inline, hot spot detection and compilation, type speculation and devirtualization, and redundant operation elimination. 1. Method inline reduces call overhead and inserts frequently called small methods directly into the call; 2. Hot spot detection and high-frequency code execution and centrally optimize it to save resources; 3. Type speculation collects runtime type information to achieve devirtualization calls, improving efficiency; 4. Redundant operations eliminate useless calculations and inspections based on operational data deletion, enhancing performance.

Instance initialization blocks are used in Java to run initialization logic when creating objects, which are executed before the constructor. It is suitable for scenarios where multiple constructors share initialization code, complex field initialization, or anonymous class initialization scenarios. Unlike static initialization blocks, it is executed every time it is instantiated, while static initialization blocks only run once when the class is loaded.

Factory mode is used to encapsulate object creation logic, making the code more flexible, easy to maintain, and loosely coupled. The core answer is: by centrally managing object creation logic, hiding implementation details, and supporting the creation of multiple related objects. The specific description is as follows: the factory mode handes object creation to a special factory class or method for processing, avoiding the use of newClass() directly; it is suitable for scenarios where multiple types of related objects are created, creation logic may change, and implementation details need to be hidden; for example, in the payment processor, Stripe, PayPal and other instances are created through factories; its implementation includes the object returned by the factory class based on input parameters, and all objects realize a common interface; common variants include simple factories, factory methods and abstract factories, which are suitable for different complexities.

There are two types of conversion: implicit and explicit. 1. Implicit conversion occurs automatically, such as converting int to double; 2. Explicit conversion requires manual operation, such as using (int)myDouble. A case where type conversion is required includes processing user input, mathematical operations, or passing different types of values ??between functions. Issues that need to be noted are: turning floating-point numbers into integers will truncate the fractional part, turning large types into small types may lead to data loss, and some languages ??do not allow direct conversion of specific types. A proper understanding of language conversion rules helps avoid errors.

Java uses wrapper classes because basic data types cannot directly participate in object-oriented operations, and object forms are often required in actual needs; 1. Collection classes can only store objects, such as Lists use automatic boxing to store numerical values; 2. Generics do not support basic types, and packaging classes must be used as type parameters; 3. Packaging classes can represent null values ??to distinguish unset or missing data; 4. Packaging classes provide practical methods such as string conversion to facilitate data parsing and processing, so in scenarios where these characteristics are needed, packaging classes are indispensable.

InJava,thefinalkeywordpreventsavariable’svaluefrombeingchangedafterassignment,butitsbehaviordiffersforprimitivesandobjectreferences.Forprimitivevariables,finalmakesthevalueconstant,asinfinalintMAX_SPEED=100;wherereassignmentcausesanerror.Forobjectref
