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

本文主要是介绍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 而是 1005
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

相关文章

SpringBoot 获取请求参数的常用注解及用法

《SpringBoot获取请求参数的常用注解及用法》SpringBoot通过@RequestParam、@PathVariable等注解支持从HTTP请求中获取参数,涵盖查询、路径、请求体、头、C... 目录SpringBoot 提供了多种注解来方便地从 HTTP 请求中获取参数以下是主要的注解及其用法:1

HTTP 与 SpringBoot 参数提交与接收协议方式

《HTTP与SpringBoot参数提交与接收协议方式》HTTP参数提交方式包括URL查询、表单、JSON/XML、路径变量、头部、Cookie、GraphQL、WebSocket和SSE,依据... 目录HTTP 协议支持多种参数提交方式,主要取决于请求方法(Method)和内容类型(Content-Ty

JWT + 拦截器实现无状态登录系统

《JWT+拦截器实现无状态登录系统》JWT(JSONWebToken)提供了一种无状态的解决方案:用户登录后,服务器返回一个Token,后续请求携带该Token即可完成身份验证,无需服务器存储会话... 目录✅ 引言 一、JWT 是什么? 二、技术选型 三、项目结构 四、核心代码实现4.1 添加依赖(pom

从原理到实战解析Java Stream 的并行流性能优化

《从原理到实战解析JavaStream的并行流性能优化》本文给大家介绍JavaStream的并行流性能优化:从原理到实战的全攻略,本文通过实例代码给大家介绍的非常详细,对大家的学习或工作具有一定的... 目录一、并行流的核心原理与适用场景二、性能优化的核心策略1. 合理设置并行度:打破默认阈值2. 避免装箱

Python实战之SEO优化自动化工具开发指南

《Python实战之SEO优化自动化工具开发指南》在数字化营销时代,搜索引擎优化(SEO)已成为网站获取流量的重要手段,本文将带您使用Python开发一套完整的SEO自动化工具,需要的可以了解下... 目录前言项目概述技术栈选择核心模块实现1. 关键词研究模块2. 网站技术seo检测模块3. 内容优化分析模

Java实现复杂查询优化的7个技巧小结

《Java实现复杂查询优化的7个技巧小结》在Java项目中,复杂查询是开发者面临的“硬骨头”,本文将通过7个实战技巧,结合代码示例和性能对比,手把手教你如何让复杂查询变得优雅,大家可以根据需求进行选择... 目录一、复杂查询的痛点:为何你的代码“又臭又长”1.1冗余变量与中间状态1.2重复查询与性能陷阱1.

Python内存优化的实战技巧分享

《Python内存优化的实战技巧分享》Python作为一门解释型语言,虽然在开发效率上有着显著优势,但在执行效率方面往往被诟病,然而,通过合理的内存优化策略,我们可以让Python程序的运行速度提升3... 目录前言python内存管理机制引用计数机制垃圾回收机制内存泄漏的常见原因1. 循环引用2. 全局变

python中的显式声明类型参数使用方式

《python中的显式声明类型参数使用方式》文章探讨了Python3.10+版本中类型注解的使用,指出FastAPI官方示例强调显式声明参数类型,通过|操作符替代Union/Optional,可提升代... 目录背景python函数显式声明的类型汇总基本类型集合类型Optional and Union(py

Python多线程应用中的卡死问题优化方案指南

《Python多线程应用中的卡死问题优化方案指南》在利用Python语言开发某查询软件时,遇到了点击搜索按钮后软件卡死的问题,本文将简单分析一下出现的原因以及对应的优化方案,希望对大家有所帮助... 目录问题描述优化方案1. 网络请求优化2. 多线程架构优化3. 全局异常处理4. 配置管理优化优化效果1.

Go语言使用Gin处理路由参数和查询参数

《Go语言使用Gin处理路由参数和查询参数》在WebAPI开发中,处理路由参数(PathParameter)和查询参数(QueryParameter)是非常常见的需求,下面我们就来看看Go语言... 目录一、路由参数 vs 查询参数二、Gin 获取路由参数和查询参数三、示例代码四、运行与测试1. 测试编程路