任务调度
Search documents
联想申请任务调度方法及装置专利,在至少两个执行设备中确定执行目标任务的目标设备
Jin Rong Jie· 2026-01-24 01:47
Core Insights - Lenovo (Beijing) Co., Ltd. has applied for a patent titled "Task Scheduling Method and Device," with publication number CN121387490A, and the application date is October 2025 [1] - The patent abstract indicates that the application provides a method and device for task scheduling, which includes obtaining task data for a target task and device attribute information for at least two execution devices [1] - The device attribute information characterizes the computing capabilities of the execution devices, which vary in terms of privacy and computing power [1] Company Overview - Lenovo (Beijing) Co., Ltd. was established in 1992 and is located in Beijing, primarily engaged in the manufacturing of computers, communications, and other electronic devices [1] - The company has a registered capital of 565 million Hong Kong dollars [1] - According to data from Tianyancha, Lenovo (Beijing) Co., Ltd. has invested in 107 companies, participated in 5,000 bidding projects, and has 1,744 trademark records and 5,000 patent records [1] - Additionally, the company holds 238 administrative licenses [1]
腾讯申请任务调度方法及相关装置专利,提高任务处理效率
Jin Rong Jie· 2025-12-04 12:13
Group 1 - Tencent Technology (Shenzhen) Co., Ltd. has applied for a patent titled "Task Scheduling Method, Device, Electronic Equipment, and Storage Medium," with publication number CN 121050841 A, and the application date is May 2024. The patent relates to computer technology, specifically a method for task scheduling that includes determining multiple candidate resources from preset resources, performing performance analysis on these resources, and data fusion processing to allocate tasks efficiently while balancing resource load and improving utilization and processing efficiency [1] Group 2 - Tencent Technology (Shenzhen) Co., Ltd. was established in 2000 and is located in Shenzhen. The company primarily engages in software and information technology services, with a registered capital of 2 million USD. It has invested in 15 companies, participated in 275 bidding projects, and holds 5,000 trademark and patent records, along with 574 administrative licenses [2]
为什么 setTimeout(0) 不是真的 0 毫秒?浏览器藏了这些“小心思”
程序员的那些事· 2025-09-14 11:04
Core Viewpoint - The article discusses the behavior of JavaScript's `setTimeout` function, highlighting that it does not execute with a true delay of 0 milliseconds, but rather has a minimum delay of approximately 4 milliseconds due to browser limitations aimed at preventing abuse and ensuring user experience [6][8]. Group 1: Timer Behavior and Limitations - Browsers impose a minimum delay of 4 milliseconds for `setTimeout` to prevent excessive battery drain and maintain page interactivity [8]. - Different browsers have varying restrictions, with older versions of Edge increasing the delay to 16 milliseconds on battery-powered devices, and Chrome imposing a 1-second delay on background tabs [8]. - A benchmark test showed that `setTimeout` in Chrome took 4.2 milliseconds, while alternatives like `MessageChannel` and `scheduler.postTask` performed significantly better [10][11]. Group 2: Alternatives to setTimeout - The article evaluates alternatives to `setTimeout`, including `setImmediate`, `MessageChannel.postMessage`, `window.postMessage`, and `scheduler.postTask`, with the latter being recommended for its ease of use and performance [9][11]. - The benchmark results indicated that `scheduler.postTask` and `MessageChannel.postMessage` had comparable performance, while `setTimeout` was consistently slower across different browsers [10][11]. Group 3: Developer Responsibility and Browser Design - There is a debate within the industry regarding whether developers should be held accountable for their code or if browsers should impose restrictions to prevent misuse of APIs like `setTimeout` [12]. - The article suggests that providing developers with better tools for task scheduling could reduce reliance on `setTimeout` and the need for browser interventions [12][13]. - The existence of the Scheduler API indicates a shift towards empowering developers while aligning with browser rendering processes [13].