Spring容器启动耗时分析 (Bean启动耗时)
spring bean 的生命周期
实例化（instantiate）, 用构造器创建一个对象 字段赋值（populate） 初始化(initialize)， 执行bean配置里的init方法或者 InitializingBean#afterPropertiesSet方法销毁（destruct）
实例化和字段赋值一般都很快，但是一些重型的bean被IOC容器创建时，需要调用远程服务或者执行耗时的操作，这些操作往往在init方法里实现。统计bean初始化耗时可以发现那些bean影响了系统的启动效率。业务方的bean可以推动业务优化，自己的bean也可以想方法优化性能。
那么如何统计初始化的耗时呢？
spring bean初始化源码分析
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory#initializeBean 观察执行初始化方法的逻辑
protected Object initializeBean(final String beanName, final Object bean, RootBeanDefinition mbd) {
if (System.getSecurityManager() != null) {
AccessController.doPrivileged(new PrivilegedAction<Object>() {
@Override
public Object run() {
invokeAwareMethods(beanName, bean);
return null;
}
}, getAccessControlContext());
}
else {
invokeAwareMethods(beanName, bean);
}
Object wrappedBean = bean;
if (mbd == null || !mbd.isSynthetic()) {
// 初始化前spring提供的系统钩子
wrappedBean = applyBeanPostProcessorsBeforeInitialization(wrappedBean, beanName);
}
try {
// 执行初始化方法
invokeInitMethods(beanName, wrappedBean, mbd);
}
catch (Throwable ex) {
throw new BeanCreationException(
(mbd != null ? mbd.getResourceDescription() : null),
beanName, "Invocation of init method failed", ex);
}
if (mbd == null || !mbd.isSynthetic()) {
// 初始化后spring提供的系统钩子
wrappedBean = applyBeanPostProcessorsAfterInitialization(wrappedBean, beanName);
}
return wrappedBean;
}
applyBeanPostProcessorsBeforeInitialization做了什么？
取出所有实现BeanPostProcessor的bean，逐个执行一遍postProcessBeforeInitialization方法。
如果您正在学习Spring Boot，那么推荐一个连载多年还在继续更新的免费教程：http://blog.didispace.com/spring-boot-learning-2x/
同理，applyBeanPostProcessorsAfterInitialization逻辑依然，只是执行的是postProcessInitialization方法。
@Override
public Object applyBeanPostProcessorsBeforeInitialization(Object existingBean, String beanName)
throws BeansException {
Object result = existingBean;
for (BeanPostProcessor beanProcessor : getBeanPostProcessors()) {
result = beanProcessor.postProcessBeforeInitialization(result, beanName);
if (result == null) {
return result;
}
}
return result;
spring系统钩子 BeanPostProcessor
Factory hook that allows for custom modification of new bean instances, e.g. checking for marker interfaces or wrapping them with proxies.
ApplicationContexts can autodetect BeanPostProcessor beans in their bean definitions and apply them to any beans subsequently created. Plain bean factories allow for programmatic registration of post-processors, applying to all beans created through this factory
BeanPostProcessor接口仅仅提供两个方法，用在在初始化bean的时候进行定制开发。
public interface BeanPostProcessor {
Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException;
Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException;
}
bean初始化耗时功能开发demo
简单demo
package org.dubbo.server.service.tool;
import com.google.common.collect.Maps;
import org.springframework.beans.BeansException;
import org.springframework.beans.factory.config.BeanPostProcessor;
import org.springframework.stereotype.Component;
import java.util.Map;
/**
* @author LvSheng
**/
@Component
public class TimeCostBeanPostProcessor implements BeanPostProcessor {
Map<String, Long> costMap = Maps.newConcurrentMap();
@Override
public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {
costMap.put(beanName, System.currentTimeMillis());
return bean;
}
@Override
public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {
long start = costMap.get(beanName);
long cost = System.currentTimeMillis() - start;
if (cost > 0) {
costMap.put(beanName, cost);
System.out.println("class: " + bean.getClass().getName()
+ "\tbean: " + beanName
+ "\ttime" + cost);
}
return bean;
}
}来源：blog.csdn.net/bruce128/article/
details/104419869
END
往期精彩Spring Boot两种方式配置 HTTPS 安全证书，你学会了么？噢，老天爷！属于Java的协程终于来了！
Java 18 新增@snipppet标签，注释中写样例代码更舒适了！
两种方式，实现 SpringBoot 中数据库密码加密
关注后端面试那些事，回复【2022面经】
获取最新大厂Java面经