SP91 Doze参数优化，延长DeviceIdleController.light的IDLE状态驻留

2024-02-09 21:18
文章标签 参数 优化 状态 延长 idle light 驻留 sp91 doze deviceidlecontroller

本文主要是介绍SP91 Doze参数优化，延长DeviceIdleController.light的IDLE状态驻留，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

唤醒现象

唤醒时刻 09:29
09-29

唤醒时刻 09:36
09-36

唤醒时刻 09:46
09-46

唤醒时刻 10:00
10-00

唤醒分析

AlarmManager android 的定时 ELAPSED_REALTIME 唤醒

设置定时器-下一个触发时刻为 1312176
11-29 09:26:23.088195   973   973 V AlarmManager: APP set(PendingIntent{d853147: PendingIntentRecord{aa3cd74 android broadcastIntent}}) : type=3 triggerAtTime=1312176 win=0 tElapsed=1312176 maxElapsed=1312176 interval=0 flags=0x1定时器触发 1312176，故台阶波形产生
11-29 09:29:33.090926   973  1213 V AlarmManager: sending alarm Alarm{fb53c89 type 3 when 1312176 android} success设置定时器-下一个触发时刻为 1492175
11-29 09:29:33.094564   973   973 V AlarmManager: APP set(PendingIntent{d853147: PendingIntentRecord{aa3cd74 android broadcastIntent}}) : type=3 triggerAtTime=1492175 win=0 tElapsed=1492175 maxElapsed=1492175 interval=0 flags=0x1
11-29 09:29:33.094939   973   973 D AlarmManager: set alarm to RTC 1492175 Type: 3定时器触发 1492175，故台阶波形产生
11-29 09:36:22.099205   973  1213 V AlarmManager: sending alarm Alarm{c4e54af type 3 when 1492175 android} success设置定时器-下一个触发时刻为 1912175
11-29 09:36:22.112267   973   973 V AlarmManager: APP set(PendingIntent{d853147: PendingIntentRecord{aa3cd74 android broadcastIntent}}) : type=3 triggerAtTime=1912175 win=0 tElapsed=1912175 maxElapsed=1912175 interval=0 flags=0x1
11-29 09:36:22.112592   973   973 D AlarmManager: set alarm to RTC 1912175 Type: 3定时器触发 1912175，故台阶波形产生
11-29 09:46:23.087939   973  1213 V AlarmManager: sending alarm Alarm{1b58ccb type 3 when 1912175 android} success设置定时器-下一个触发时刻为 2512176
11-29 09:46:23.098627   973   973 V AlarmManager: APP set(PendingIntent{d853147: PendingIntentRecord{aa3cd74 android broadcastIntent}}) : type=3 triggerAtTime=2512176 win=0 tElapsed=2512176 maxElapsed=2512176 interval=0 flags=0x1
11-29 09:46:23.099062   973   973 D AlarmManager: set alarm to RTC 2512176 Type: 3定时器触发 2512176，故台阶波形产生
11-29 10:00:01.093812   973  1213 V AlarmManager: sending alarm Alarm{c7af3c1 type 3 when 2512176 android} success设置定时器-下一个触发时刻为 3352176
11-29 10:00:01.098752   973   973 V AlarmManager: APP set(PendingIntent{d853147: PendingIntentRecord{aa3cd74 android broadcastIntent}}) : type=3 triggerAtTime=3352176 win=0 tElapsed=3352176 maxElapsed=3352176 interval=0 flags=0x1
11-29 10:00:01.099113   973   973 D AlarmManager: set alarm to RTC 3352176 Type: 3定时器触发 3352176，但是波形图不是 10:11 而是 10 ：05
11-29 10:11:54.766607   973   973 V AlarmManager: sending alarm Alarm{22c0f4a type 3 when 3352176 android} success

DeviceIdleController.light 定时器 ELAPSED_REALTIME_WAKEUP 唤醒

DeviceIdleController.light 设置定时器-下一个触发时刻为 1464102
11-29 09:24:31.927   973   973 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=1464102 win=-1 tElapsed=1464102 maxElapsed=1689101 interval=0 flags=0x8
11-29 09:26:23.078   973  1213 D AlarmManager: set alarm to RTC 1464102 Type: 2定时器触发 1464102，故台阶波形产生，且满足波形图时间
11-29 09:29:33.093   973  1213 D AlarmManager: wakeup alarm = Alarm{392b48e type 2 when 1464102 android}; listener package = DeviceIdleController.lightneedGrouping = falseDeviceIdleController.light 设置定时器-下一个触发时刻为 1765269
11-29 09:29:33.111   973  1003 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=1765269 win=-1 tElapsed=1765269 maxElapsed=1990269 interval=0 flags=0x8定时器触发 1765269，故台阶波形产生，且满足波形图时间
11-29 09:36:22.102   973  1213 D AlarmManager: wakeup alarm = Alarm{98190bc type 2 when 1765269 android}; listener package = DeviceIdleController.lightneedGrouping = falseDeviceIdleController.light 设置定时器-下一个触发时刻为 2474279
11-29 09:36:22.110   973  1003 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=2474279 win=-1 tElapsed=2474279 maxElapsed=2924273 interval=0 flags=0x8
11-29 09:36:22.111   973  1003 D AlarmManager: set alarm to RTC 2474279 Type: 2DeviceIdleController.light 设置定时器-下一个触发时刻为 2535269
11-29 09:46:23.094   973  1003 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=2535269 win=-1 tElapsed=2535269 maxElapsed=2580268 interval=0 flags=0x8
11-29 09:46:23.098   973  1003 D AlarmManager: set alarm to RTC 2535269 Type: 2DeviceIdleController.light 设置定时器-下一个触发时刻为 3080487
11-29 09:46:28.312   973  1003 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=3080487 win=-1 tElapsed=3080487 maxElapsed=3530487 interval=0 flags=0x8定时器触发 3080487，故台阶波形产生，且满足波形图时间
11-29 10:00:01.094   973  1213 D AlarmManager: wakeup alarm = Alarm{ee4c766 type 2 when 3080487 android}; listener package = DeviceIdleController.lightneedGrouping = falseDeviceIdleController.light 设置定时器-下一个触发时刻为 4193320
11-29 10:00:01.145   973  1003 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=4193320 win=-1 tElapsed=4193320 maxElapsed=4868320 interval=0 flags=0x811-29 10:00:01.146   973  1003 D AlarmManager: set alarm to RTC 4193320 Type: 2

题外-定时器类型

83public class AlarmManager {
84    private static final String TAG = "AlarmManager";
85
86    /**
87     * Alarm time in {@link System#currentTimeMillis System.currentTimeMillis()}
88     * (wall clock time in UTC), which will wake up the device when
89     * it goes off.
90     */
91    public static final int RTC_WAKEUP = 0;
92    /**
93     * Alarm time in {@link System#currentTimeMillis System.currentTimeMillis()}
94     * (wall clock time in UTC).  This alarm does not wake the
95     * device up; if it goes off while the device is asleep, it will not be
96     * delivered until the next time the device wakes up.
97     */
98    public static final int RTC = 1;
99    /**
100     * Alarm time in {@link android.os.SystemClock#elapsedRealtime
101     * SystemClock.elapsedRealtime()} (time since boot, including sleep),
102     * which will wake up the device when it goes off.
103     */
104    public static final int ELAPSED_REALTIME_WAKEUP = 2;
105    /**
106     * Alarm time in {@link android.os.SystemClock#elapsedRealtime
107     * SystemClock.elapsedRealtime()} (time since boot, including sleep).
108     * This alarm does not wake the device up; if it goes off while the device
109     * is asleep, it will not be delivered until the next time the device
110     * wakes up.
111     */
112    public static final int ELAPSED_REALTIME = 3

源码分析

定时器相关源码

/frameworks/base/services/core/java/com/android/server/AlarmManagerService.java

    void setImpl(int type, long triggerAtTime, long windowLength, long interval,PendingIntent operation, IAlarmListener directReceiver, String listenerTag,int flags, WorkSource workSource, AlarmManager.AlarmClockInfo alarmClock,int callingUid, String callingPackage) {synchronized (mLock) {if (true) {if (operation == null) {Slog.v(TAG, "APP set with listener(" + listenerTag + ") : type=" + type+ " triggerAtTime=" + triggerAtTime + " win=" + windowLength+ " tElapsed=" + triggerElapsed + " maxElapsed=" + maxElapsed+ " interval=" + interval + " flags=0x" + Integer.toHexString(flags));} else {Slog.v(TAG, "APP set(" + operation + ") : type=" + type+ " triggerAtTime=" + triggerAtTime + " win=" + windowLength+ " tElapsed=" + triggerElapsed + " maxElapsed=" + maxElapsed+ " interval=" + interval + " flags=0x" + Integer.toHexString(flags));}}setImplLocked(type, triggerAtTime, triggerElapsed, windowLength, maxElapsed,interval, operation, directReceiver, listenerTag, flags, true, workSource,alarmClock, callingUid, callingPackage, mNeedGrouping);}

DeviceIdleController 设置定时

frameworks\base\services\core\java\com\android\server\DeviceIdleController.java

package com.android.server;/*** Keeps track of device idleness and drives low power mode based on that.*/
public class DeviceIdleController extends SystemServiceimplements AnyMotionDetector.DeviceIdleCallback {void scheduleLightAlarmLocked(long delay) {if (DEBUG) Slog.d(TAG, "scheduleLightAlarmLocked(" + delay + ")");mNextLightAlarmTime = SystemClock.elapsedRealtime() + delay;mAlarmManager.set(AlarmManager.ELAPSED_REALTIME_WAKEUP,mNextLightAlarmTime, "DeviceIdleController.light", mLightAlarmListener, mHandler);}

源码修改

我们可以延长 IDLE 模式的驻留时间， 单位时间内减少其LIGHT_STATE_IDLE to LIGHT_STATE_IDLE_MAINTENANCE或LIGHT_WAITING_FOR_NETWORK的次数，优化电池

package com.android.server;/*** Keeps track of device idleness and drives low power mode based on that.*/
public class DeviceIdleController extends SystemServiceimplements AnyMotionDetector.DeviceIdleCallback {private static final boolean DEBUG = true;// LIGHT_IDLE 的驻留时间是 [15, 30]分钟// suhuazhi,20171220, for extend duration of idleLIGHT_IDLE_TIMEOUT = mParser.getLong(KEY_LIGHT_IDLE_TIMEOUT,!COMPRESS_TIME ? 15 * 60 * 1000L : 15 * 1000L);LIGHT_IDLE_FACTOR = mParser.getFloat(KEY_LIGHT_IDLE_FACTOR,3f);LIGHT_MAX_IDLE_TIMEOUT = mParser.getLong(KEY_LIGHT_MAX_IDLE_TIMEOUT,!COMPRESS_TIME ? 30 * 60 * 1000L : 60 * 1000L);// end if
=======================================================================================
// 原来的 LIGHT_IDLE 的驻留时间是 [5, 15]分钟LIGHT_IDLE_TIMEOUT = mParser.getLong(KEY_LIGHT_IDLE_TIMEOUT,!COMPRESS_TIME ? 5 * 60 * 1000L : 15 * 1000L);LIGHT_IDLE_FACTOR = mParser.getFloat(KEY_LIGHT_IDLE_FACTOR,2f);LIGHT_MAX_IDLE_TIMEOUT = mParser.getLong(KEY_LIGHT_MAX_IDLE_TIMEOUT,!COMPRESS_TIME ? 15 * 60 * 1000L : 60 * 1000L);

延长对应的 延长 IDLE 模式的驻留时间

======================================================================switch (mLightState) {case LIGHT_STATE_INACTIVE:// Reset the upcoming idle delays.mNextLightIdleDelay = mConstants.LIGHT_IDLE_TIMEOUT;break;case LIGHT_STATE_PRE_IDLE:case LIGHT_STATE_IDLE_MAINTENANCE:.......scheduleLightAlarmLocked(mNextLightIdleDelay);mNextLightIdleDelay = Math.min(mConstants.LIGHT_MAX_IDLE_TIMEOUT,(long)(mNextLightIdleDelay * mConstants.LIGHT_IDLE_FACTOR));if (mNextLightIdleDelay < mConstants.LIGHT_IDLE_TIMEOUT) {mNextLightIdleDelay = mConstants.LIGHT_IDLE_TIMEOUT;}.....if (DEBUG) Slog.d(TAG, "Moved to LIGHT_STATE_IDLE. mNextLightIdleDelay = " + mNextLightIdleDelay);mLightState = LIGHT_STATE_IDLE;break;case LIGHT_STATE_WAITING_FOR_NETWORK:if (mNetworkConnected || mLightState == LIGHT_STATE_WAITING_FOR_NETWORK) {} else {// We'd like to do maintenance, but currently don't have network// connectivity...  let's try to wait until the network comes back.// We'll only wait for another full idle period, however, and then give up.scheduleLightAlarmLocked(mNextLightIdleDelay);if (DEBUG) Slog.d(TAG, "Moved to LIGHT_WAITING_FOR_NETWORK. mNextLightIdleDelay = " + mNextLightIdleDelay);mLightState = LIGHT_STATE_WAITING_FOR_NETWORK;}======================================================================

优化效果

优化前数据
  • Doze的状态切换
3,108: 11-29 14:59:18.953134   964   964 D DeviceIdleController: Moved from STATE_ACTIVE to STATE_INACTIVE 
3,111: 11-29 14:59:18.953422   964   964 D DeviceIdleController: Moved from LIGHT_STATE_ACTIVE to LIGHT_STATE_INACTIVE 
3,197: 11-29 15:04:20.131240   964   992 D DeviceIdleController: Moved to LIGHT_STATE_IDLE. 
<5分钟间隔>
3,229: 11-29 15:09:21.098920   964   992 D DeviceIdleController: Moved to LIGHT_WAITING_FOR_NETWORK. 
<15分钟间隔>
3,262: 11-29 15:26:07.132630   964   992 D DeviceIdleController: Moved from LIGHT_STATE_IDLE to LIGHT_STATE_IDLE_MAINTENANCE. 
3,276: 11-29 15:26:12.319049   964   992 D DeviceIdleController: Moved to LIGHT_STATE_IDLE. 
<10分钟间隔>
3,314: 11-29 15:36:13.122641   964   992 D DeviceIdleController: Moved to LIGHT_WAITING_FOR_NETWORK. 
<15分钟间隔>
3,331: 11-29 15:51:14.110387   964   992 D DeviceIdleController: Moved from LIGHT_STATE_IDLE to LIGHT_STATE_IDLE_MAINTENANCE. 
3,353: 11-29 15:51:19.297282   964   992 D DeviceIdleController: Moved to LIGHT_STATE_IDLE. 
<20分钟间隔>
3,419: 11-29 16:10:21.125400   964   992 D DeviceIdleController: Moved to LIGHT_WAITING_FOR_NETWORK. 
<15分钟间隔>
3,455: 11-29 16:26:07.140463   964   992 D DeviceIdleController: Moved from LIGHT_STATE_IDLE to LIGHT_STATE_IDLE_MAINTENANCE. 
3,469: 11-29 16:26:12.304652   964   992 D DeviceIdleController: Moved to LIGHT_STATE_IDLE.
  • 唤醒时间间隔
    总时长 1小时半
3,113: 11-29 14:59:18.953767   964   964 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=565319 win=-1 tElapsed=565319 maxElapsed=790319 interval=0 flags=0x8 
3,193: 11-29 15:04:20.104443   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=866461 win=-1 tElapsed=866461 maxElapsed=1091461 interval=0 flags=0x8 
<5分钟间隔>
3,228: 11-29 15:09:21.098108   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=1467463 win=-1 tElapsed=1467463 maxElapsed=1917463 interval=0 flags=0x8 
<15分钟间隔>
3,254: 11-29 15:26:07.126923   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=1933461 win=-1 tElapsed=1933461 maxElapsed=1978461 interval=0 flags=0x8 
3,272: 11-29 15:26:12.313214   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=2478678 win=-1 tElapsed=2478678 maxElapsed=2928678 interval=0 flags=0x8 
<10分钟间隔>
3,312: 11-29 15:36:13.120175   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=3379485 win=-1 tElapsed=3379485 maxElapsed=4054485 interval=0 flags=0x8 
<15分钟间隔>
3,329: 11-29 15:51:14.105569   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=3495252 win=-1 tElapsed=3495252 maxElapsed=3581337 interval=0 flags=0x8 
3,350: 11-29 15:51:19.291767   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=4285656 win=-1 tElapsed=4285656 maxElapsed=4960656 interval=0 flags=0x8 
<20分钟间隔>
3,416: 11-29 16:10:21.116175   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=5427480 win=-1 tElapsed=5427480 maxElapsed=6102480 interval=0 flags=0x8 
<15分钟间隔>
3,447: 11-29 16:26:07.128173   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=5643059 win=-1 tElapsed=5643059 maxElapsed=5770233 interval=0 flags=0x8 
3,465: 11-29 16:26:12.299088   964   992 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=6378664 win=-1 tElapsed=6378664 maxElapsed=7053664 interval=0 flags=0x8
优化后数据，预计拉长上述的时间间隔
  • Doze的状态切换
2,041: 01-01 02:30:51.073802   977   977 D DeviceIdleController: Moved from STATE_ACTIVE to STATE_INACTIVE 
2,044: 01-01 02:30:51.074208   977   977 D DeviceIdleController: Moved from LIGHT_STATE_ACTIVE to LIGHT_STATE_INACTIVE 
2,866: 12-29 18:42:10.965973   977   977 D DeviceIdleController: Moved from STATE_ACTIVE to STATE_INACTIVE 
2,869: 12-29 18:42:10.966274   977   977 D DeviceIdleController: Moved from LIGHT_STATE_ACTIVE to LIGHT_STATE_INACTIVE 
<5分钟间隔>
2,934: 12-29 18:47:12.144441   977  1005 D DeviceIdleController: Moved to scheduleLightAlarmLocked mNextLightIdleDelay 900000 
2,935: 12-29 18:47:12.144598   977  1005 D DeviceIdleController: Moved to LIGHT_STATE_IDLE. mNextLightIdleDelay 1800000 
<15分钟间隔>
2,980: 12-29 19:02:13.117638   977  1005 D DeviceIdleController: Moved to LIGHT_WAITING_FOR_NETWORK. mNextLightIdleDelay = 1800000 
<30分钟间隔>
3,015: 12-29 19:32:14.151051   977  1005 D DeviceIdleController: Moved from LIGHT_STATE_IDLE to LIGHT_STATE_IDLE_MAINTENANCE. 
3,033: 12-29 19:32:19.319212   977  1005 D DeviceIdleController: Moved to scheduleLightAlarmLocked mNextLightIdleDelay 1800000 
3,034: 12-29 19:32:19.319374   977  1005 D DeviceIdleController: Moved to LIGHT_STATE_IDLE. mNextLightIdleDelay 1800000
  • 唤醒时间间隔
2,871: 12-29 18:42:10.966672   977   977 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=3887071 win=-1 tElapsed=3887071 maxElapsed=4112071 interval=0 flags=0x8 
<5分钟间隔>
2,931: 12-29 18:47:12.133963   977  1005 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=4788238 win=-1 tElapsed=4788238 maxElapsed=5463238 interval=0 flags=0x8 
<15分钟间隔>
2,978: 12-29 19:02:13.103318   977  1005 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=6589207 win=-1 tElapsed=6589207 maxElapsed=7939207 interval=0 flags=0x8 
<30分钟间隔>
3,013: 12-29 19:32:14.149906   977  1005 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=6650253 win=-1 tElapsed=6650253 maxElapsed=6695252 interval=0 flags=0x8 
3,030: 12-29 19:32:19.313706   977  1005 V AlarmManager: APP set with listener(DeviceIdleController.light) : type=2 triggerAtTime=8395418 win=-1 tElapsed=8395418 maxElapsed=9745418 interval=0 flags=0x8

优化后，相同时长下，唤醒次数少了一半，且主要是拉长LIGHT_STATE_IDLE待机的驻留期，让LIGHT_WAITING_FOR_NETWORK和LIGHT_STATE_IDLE_MAINTENANCE的状态少一些刷新
但是又不对有网络下的MAINTENANCE造成太大影响

这篇关于SP91 Doze参数优化，延长DeviceIdleController.light的IDLE状态驻留的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！


http://www.chinasem.cn/article/695311。

相关文章

SpringBoot3实现Gzip压缩优化的技术指南

SpringBoot3实现Gzip压缩优化的技术指南

《SpringBoot3实现Gzip压缩优化的技术指南》随着Web应用的用户量和数据量增加,网络带宽和页面加载速度逐渐成为瓶颈,为了减少数据传输量,提高用户体验,我们可以使用Gzip压缩HTTP响应,... 目录1、简述2、配置2.1 添加依赖2.2 配置 Gzip 压缩3、服务端应用4、前端应用4.1 N
阅读更多...
Spring Boot + MyBatis Plus 高效开发实战从入门到进阶优化(推荐)

Spring Boot + MyBatis Plus 高效开发实战从入门到进阶优化(推荐)

《SpringBoot+MyBatisPlus高效开发实战从入门到进阶优化(推荐)》本文将详细介绍SpringBoot+MyBatisPlus的完整开发流程,并深入剖析分页查询、批量操作、动... 目录Spring Boot + MyBATis Plus 高效开发实战：从入门到进阶优化1. MyBatis
阅读更多...
MyBatis 动态 SQL 优化之标签的实战与技巧(常见用法)

MyBatis 动态 SQL 优化之标签的实战与技巧(常见用法)

《MyBatis动态SQL优化之标签的实战与技巧(常见用法)》本文通过详细的示例和实际应用场景,介绍了如何有效利用这些标签来优化MyBatis配置,提升开发效率,确保SQL的高效执行和安全性,感... 目录动态SQL详解一、动态SQL的核心概念1.1 什么是动态SQL？1.2 动态SQL的优点1.3 动态S
阅读更多...
Python如何使用__slots__实现节省内存和性能优化

Python如何使用__slots__实现节省内存和性能优化

《Python如何使用__slots__实现节省内存和性能优化》你有想过,一个小小的__slots__能让你的Python类内存消耗直接减半吗,没错,今天咱们要聊的就是这个让人眼前一亮的技巧,感兴趣的... 目录背景：内存吃得满满的类__slots__：你的内存管理小助手举个大概的例子：看看效果如何？1.
阅读更多...
一文详解SpringBoot响应压缩功能的配置与优化

一文详解SpringBoot响应压缩功能的配置与优化

《一文详解SpringBoot响应压缩功能的配置与优化》SpringBoot的响应压缩功能基于智能协商机制,需同时满足很多条件,本文主要为大家详细介绍了SpringBoot响应压缩功能的配置与优化,需... 目录一、核心工作机制1.1 自动协商触发条件1.2 压缩处理流程二、配置方案详解2.1 基础YAML
阅读更多...
MySQL中慢SQL优化的不同方式介绍

MySQL中慢SQL优化的不同方式介绍

《MySQL中慢SQL优化的不同方式介绍》慢SQL的优化,主要从两个方面考虑,SQL语句本身的优化,以及数据库设计的优化,下面小编就来给大家介绍一下有哪些方式可以优化慢SQL吧... 目录避免不必要的列分页优化索引优化JOIN 的优化排序优化UNION 优化慢 SQL 的优化，主要从两个方面考虑，SQL 语
阅读更多...
一文带你了解SpringBoot中启动参数的各种用法

一文带你了解SpringBoot中启动参数的各种用法

《一文带你了解SpringBoot中启动参数的各种用法》在使用SpringBoot开发应用时,我们通常需要根据不同的环境或特定需求调整启动参数,那么,SpringBoot提供了哪些方式来配置这些启动参... 目录一、启动参数的常见传递方式二、通过命令行参数传递启动参数三、使用 application.pro
阅读更多...
MySQL中慢SQL优化方法的完整指南

MySQL中慢SQL优化方法的完整指南

《MySQL中慢SQL优化方法的完整指南》当数据库响应时间超过500ms时,系统将面临三大灾难链式反应,所以本文将为大家介绍一下MySQL中慢SQL优化的常用方法,有需要的小伙伴可以了解下... 目录一、慢SQL的致命影响二、精准定位问题SQL1. 启用慢查询日志2. 诊断黄金三件套三、六大核心优化方案方案
阅读更多...
Redis中高并发读写性能的深度解析与优化

Redis中高并发读写性能的深度解析与优化

《Redis中高并发读写性能的深度解析与优化》Redis作为一款高性能的内存数据库,广泛应用于缓存、消息队列、实时统计等场景,本文将深入探讨Redis的读写并发能力,感兴趣的小伙伴可以了解下... 目录引言一、Redis 并发能力概述1.1 Redis 的读写性能1.2 影响 Redis 并发能力的因素二、
阅读更多...
基于@RequestParam注解之Spring MVC参数绑定的利器

基于@RequestParam注解之Spring MVC参数绑定的利器

《基于@RequestParam注解之SpringMVC参数绑定的利器》：本文主要介绍基于@RequestParam注解之SpringMVC参数绑定的利器,具有很好的参考价值,希望对大家有所帮助... 目录@RequestParam注解：Spring MVC参数绑定的利器什么是@RequestParam？@
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2