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。

相关文章

详解Spring Boot接收参数的19种方式

详解Spring Boot接收参数的19种方式

《详解SpringBoot接收参数的19种方式》SpringBoot提供了多种注解来接收不同类型的参数,本文给大家介绍SpringBoot接收参数的19种方式,感兴趣的朋友跟随小编一起看看吧... 目录SpringBoot接受参数相关@PathVariable注解@RequestHeader注解@Reque
阅读更多...
Java向kettle8.0传递参数的方式总结

Java向kettle8.0传递参数的方式总结

《Java向kettle8.0传递参数的方式总结》介绍了如何在Kettle中传递参数到转换和作业中,包括设置全局properties、使用TransMeta和JobMeta的parameterValu... 目录1.传递参数到转换中2.传递参数到作业中总结1.传递参数到转换中1.1. 通过设置Trans的
阅读更多...
java如何调用kettle设置变量和参数

java如何调用kettle设置变量和参数

《java如何调用kettle设置变量和参数》文章简要介绍了如何在Java中调用Kettle,并重点讨论了变量和参数的区别,以及在Java代码中如何正确设置和使用这些变量,避免覆盖Kettle中已设置... 目录Java调用kettle设置变量和参数java代码中变量会覆盖kettle里面设置的变量总结ja
阅读更多...
正则表达式高级应用与性能优化记录

正则表达式高级应用与性能优化记录

《正则表达式高级应用与性能优化记录》本文介绍了正则表达式的高级应用和性能优化技巧,包括文本拆分、合并、XML/HTML解析、数据分析、以及性能优化方法,通过这些技巧,可以更高效地利用正则表达式进行复杂... 目录第6章：正则表达式的高级应用6.1 模式匹配与文本处理6.1.1 文本拆分6.1.2 文本合并6
阅读更多...
spring 参数校验Validation示例详解

spring 参数校验Validation示例详解

《spring参数校验Validation示例详解》Spring提供了Validation工具类来实现对客户端传来的请求参数的有效校验,本文给大家介绍spring参数校验Validation示例详... 目录前言一、Validation常见的校验注解二、Validation的简单应用三、分组校验四、自定义校
阅读更多...
SpringBoot中Get请求和POST请求接收参数示例详解

SpringBoot中Get请求和POST请求接收参数示例详解

《SpringBoot中Get请求和POST请求接收参数示例详解》文章详细介绍了SpringBoot中Get请求和POST请求的参数接收方式,包括方法形参接收参数、实体类接收参数、HttpServle... 目录1、Get请求1.1 方法形参接收参数 这种方式一般适用参数比较少的情况，并且前后端参数名称必须
阅读更多...
Vue3 的 shallowRef 和 shallowReactive：优化性能

Vue3 的 shallowRef 和 shallowReactive：优化性能

大家对 Vue3 的 ref 和 reactive 都很熟悉，那么对 shallowRef 和 shallowReactive 是否了解呢？ 在编程和数据结构中，“shallow”（浅层）通常指对数据结构的最外层进行操作，而不递归地处理其内部或嵌套的数据。这种处理方式关注的是数据结构的第一层属性或元素，而忽略更深层次的嵌套内容。 1. 浅层与深层的对比 1.1 浅层（Shallow） 定义
阅读更多...
HDFS—存储优化（纠删码）

HDFS—存储优化（纠删码）

纠删码原理 HDFS 默认情况下，一个文件有3个副本，这样提高了数据的可靠性，但也带来了2倍的冗余开销。 Hadoop3.x 引入了纠删码，采用计算的方式，可以节省约50％左右的存储空间。 此种方式节约了空间，但是会增加 cpu 的计算。 纠删码策略是给具体一个路径设置。所有往此路径下存储的文件，都会执行此策略。 默认只开启对 RS-6-3-1024k
阅读更多...
hdu1043（八数码问题，广搜 + hash（实现状态压缩） ）

hdu1043（八数码问题，广搜 + hash（实现状态压缩） ）

利用康拓展开将一个排列映射成一个自然数，然后就变成了普通的广搜题。 #include<iostream>#include<algorithm>#include<string>#include<stack>#include<queue>#include<map>#include<stdio.h>#include<stdlib.h>#include<ctype.h>#inclu
阅读更多...
使用opencv优化图片（画面变清晰）

使用opencv优化图片（画面变清晰）

文章目录 需求影响照片清晰度的因素 实现降噪测试代码 锐化空间锐化Unsharp Masking频率域锐化对比测试 对比度增强常用算法对比测试 需求 对图像进行优化，使其看起来更清晰，同时保持尺寸不变，通常涉及到图像处理技术如锐化、降噪、对比度增强等 影响照片清晰度的因素 影响照片清晰度的因素有很多，主要可以从以下几个方面来分析 1. 拍摄设备 相机传感器：相机传
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2