A PHP timed task management method and system

Abstract

Embodiments of the present invention provide a PHP timed task management method and system, the method comprising: executing a PHP entry file according to a set time period; obtaining all PHP class files under the PHP entry file directory, and analyzing them by using a reflection mechanism An annotation of each PHP class file execution method; according to the annotation of the execution method, execute the PHP class file; after the execution of the PHP class file is completed, record the execution completion time of the PHP class file. This technical solution performs file execution control through file comment analysis, which greatly reduces the workload and operation and maintenance costs.

Description

technical field [0001] The invention belongs to the technical field of computers, and in particular relates to a PHP timing task management method and system. Background technique [0002] At present, most Internet companies use the native program command crontab of the linux operating system to manage the timing tasks in the English hypertext preprocessing language PHP (Hypertext Preprocessor) project. It is necessary to configure the execution command and execution cycle of each task in the linux crontab, relying on the linux system Scheduling to complete the execution of each timed task, the solution based on linux crontab has become the mainstream of PHP project timed task management. [0003] Although the solution based on linux crontab is the mainstream solution for timing task management of PHP projects, it has three obvious defects: [0004] 1. Does not support dependent scheduling: linux crontab randomly starts tasks at the same time, that is, the start timing of t...

AI Technical Summary

Problems solved by technology

[0004] 1. Does not support dependent scheduling: linux crontab randomly starts tasks at the same time, that is, the start timing of tasks A and B started at the same time is random, and does not support task B after task A is executed, that is, it does not support Basic Dependency Scheduling Mechanism

[0005] 2. The configuration is not transparent enough: the linux crontab configuration is all in the configuration file of the linux server, which is generally managed by the operation and maintenance personnel, and the R&D personnel cannot directly and clearly know the configuration content

[0006] 3. High maintenance cost: Every time you add, modify, or delete a scheduled task, you need to modify the crontab configuration of the server. For cluster services, you need to modify the configuration files of all machines in the cluster, and the maintenance cost is obviously high.

Images