CN110716798A

CN110716798A - PHP (hypertext preprocessor) timing task management method and system

Info

Publication number: CN110716798A
Application number: CN201910930173.6A
Authority: CN
Inventors: 唐俊; 彭冬
Original assignee: Weimeng Chuangke Network Technology China Co Ltd
Current assignee: Weimeng Chuangke Network Technology China Co Ltd
Priority date: 2019-09-29
Filing date: 2019-09-29
Publication date: 2020-01-21
Anticipated expiration: 2039-09-29
Also published as: CN110716798B

Abstract

The embodiment of the invention provides a PHP timing task management method and a system, wherein the method comprises the following steps: executing the PHP entry file according to a set time period; acquiring all PHP files in the PHP entry file directory, and analyzing the annotation of each PHP file execution method by using a reflection mechanism; executing the PHP class file according to the annotation of the execution method; and after the execution of the PHP type file is finished, recording the execution finishing time of the PHP type file. According to the technical scheme, file execution control is performed through file annotation and analysis, and the workload and the operation and maintenance cost are greatly reduced.

Description

PHP (hypertext preprocessor) timing task management method and system

Technical Field

The invention belongs to the technical field of computers, and particularly relates to a PHP (hypertext preprocessor) timing task management method and system.

Background

Currently, most internet companies adopt linux operating system native program instructions, crontab, to manage timing tasks in the php (hypertext preprocessor) project, an execution command and an execution cycle of each task need to be configured in the linux crontab, and the execution of each timing task is completed by means of the scheduling of a linux system.

The linux crottab-based solution, although the mainstream solution for timing task management of the php project, has three obvious defects:

1. dependent scheduling is not supported: the linux crontab starts the tasks at the same time randomly, that is, the starting time of the tasks a and B started at the same time is random, and cannot support the task a to execute the task B after the task a is executed, that is, a basic dependent scheduling mechanism is not supported.

2. The configuration is not transparent enough: the linux crontab configuration is completely in the configuration file of the linux server and is generally managed by operation and maintenance personnel, and the developer cannot directly know the configuration content.

3. The maintenance cost is high: each time operations such as adding, modifying, deleting and the like to the timing task need to modify the crontab configuration of the server, and for the cluster service, configuration files of all machines in the cluster need to be modified, so that the maintenance cost is obviously higher.

Disclosure of Invention

The embodiment of the invention provides a PHP timing task management method and a PHP timing task management system, which can be used for controlling file execution through file annotation and analysis, thereby greatly reducing the workload and the operation and maintenance cost.

In order to achieve the above object, in one aspect, an embodiment of the present invention provides a PHP timing task management method, where the method includes:

executing the PHP entry file according to a set time period;

acquiring all PHP files in the PHP entry file directory, and analyzing the annotation of each PHP file execution method by using a reflection mechanism;

executing the PHP class file according to the annotation of the execution method;

and after the execution of the PHP type file is finished, recording the execution finishing time of the PHP type file.

In another aspect, an embodiment of the present invention provides a PHP timed task management system, where the system includes:

the portal file execution unit is used for executing the PHP portal file according to a set time period;

the class file acquisition unit is used for acquiring all PHP class files in the PHP entry file directory and analyzing the annotation of each PHP class file execution method by using a reflection mechanism;

a class file executing unit, configured to execute the PHP class file according to the comment of the execution method;

and the completion time recording unit is used for recording the execution completion time of the PHP files after the execution of the PHP files is completed.

The technical scheme has the following beneficial effects:

compared with the current mainstream timing task management scheme, the scheme defines the dependent tasks through annotations, and then performs logic processing before the tasks are started, so that simple dependent scheduling can be realized. Secondly, according to the scheme, the task execution period configuration is written in the comments of the class methods, so that the method is transparent to developers, the problem of high operation and maintenance cost is solved, the follow-up operations of newly adding, modifying, deleting tasks and the like only need to modify the comments instead of the configuration modification of the full server system, and the workload and the operation and maintenance cost are greatly reduced.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a flowchart of a PHP timing task management method according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of a PHP timing task management system according to an embodiment of the present invention;

fig. 3 is a schematic structural diagram of a class file execution unit in the PHP timed task management system according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

In the scheme, linux crontab is not completely abandoned, a unified entry is made by using the crontab to execute the entry file of the php, then the execution cycle configuration and the dependency configuration of each timing task are written in the annotation of the php method, the annotation is analyzed by using the reflection mechanism of the php, then the scheduling is performed in the entry file of the php task, and the flow is described in detail below.

As shown in fig. 1, it is a flowchart of a PHP timing task management method according to an embodiment of the present invention, where the method includes:

and S101, executing the PHP entry file according to a set time period.

Specifically, according to a set time period, an execution instruction of the PHP entry file is started through a program instruction crontab of the operating system linux.

The execution command of the PHP entry file is configured by using linux condntab, the execution cycle is executed once per minute, and the specific configuration is as follows:

*****/php/bin/php/path/to/cli.php

the syntax of linux conntab represents once per minute, php/bin/php represents the position of php executable file in the system, and/path/to/cli.

Since we are configured to execute the portal file once every minute, linux condtab will start the PHP portal file when the opportunity comes.

S102, acquiring all PHP files in the PHP entry file directory, and analyzing the annotation of each PHP file execution method by using a reflection mechanism; the note of the PHP class file execution method comprises an execution cycle and a dependency method corresponding to the PHP class file.

All timed tasks are written in the same directory of the entry file, so that all php files in the directory of the entry file can be obtained after the entry file is started.

For example:

class methods cron1 and cron2 are defined above, the execution period of cron1 is once every 5 minutes, cron1 depends on cron2, and cron2 is also executed once every 5 minutes, and no method is relied on.

S103, executing the PHP file according to the annotation of the execution method.

Judging whether the PHP file enters a current execution period in time or not according to the previous execution time and the execution period of the PHP file; judging whether the PHP file has a method for relying on the PHP file according to the method for relying on the PHP file;

for a PHP class file without a dependent method, when entering a current execution cycle, executing the PHP class file;

for the PHP class file with the dependent method, when the current execution cycle is entered and the method dependent on the PHP class file is executed, the PHP class file is executed.

Specifically, according to the execution cycle in the comment, since the execution cycle of each task is known, it can be determined whether the current execution should continue according to the last execution time of the task, if the current time is less than one execution cycle from the last execution completion time, the current task is directly terminated, otherwise, the current task continues.

And according to the dependent configuration of the dependent method, whether the current task has a dependent task or not can be known, if the dependent task exists, the current task can be executed only by waiting for the dependent task to be executed preferentially, otherwise, the current task is continued.

After the execution period and the dependent method in the annotation are analyzed, the class method of the corresponding task is directly executed, but the execution sequence needs to be noticed, all the dependent class file methods are executed firstly, a pop function can be used for starting a new process to be executed concurrently, then the class file methods which do not depend on other class file methods are also executed concurrently in a pop mode, and finally the class file methods which depend on other methods are executed, and are also executed concurrently in a pop mode.

And S104, recording the execution completion time of the PHP file after the execution of the PHP file is completed.

The execution completion time of the PHP class file is a unix timestamp of a system when the execution of the PHP class file is completed; after the execution of the PHP class file is completed, recording the execution completion time of the PHP class file, including:

for a PHP type file deployed by a single machine, writing the execution completion time of the PHP type file into a local file of a system; for a PHP type file deployed by multiple machines, writing the execution completion time of the PHP type file into a mysql database or a distributed application program coordination service zookeeper. The execution completion time is used for determining whether the execution cycle limit is met when the task is started next time, and the reliability of the storage is particularly important.

Corresponding to the above method, as shown in fig. 2, it is a schematic diagram of a PHP timing task management system according to an embodiment of the present invention, where the system includes:

an entry file execution unit 11, configured to execute the PHP entry file according to a set time period;

a class file acquiring unit 12, configured to acquire all PHP class files in the PHP entry file directory, and analyze an annotation of an execution method of each PHP class file by using a reflection mechanism;

a class file executing unit 13, configured to execute the PHP class file according to the comment of the execution method;

and a completion time recording unit 14, configured to record the execution completion time of the PHP class file after the execution of the PHP class file is completed.

Further, the entry file executing unit 11 is specifically configured to:

and starting an execution instruction of the PHP entry file through a program instruction crontab of the operating system linux according to a set time period.

Further, the note of the PHP class file execution method includes an execution cycle and a dependent method of the corresponding PHP class file.

Further, the class file executing unit 13 includes:

the determining module 131 is configured to determine whether the PHP class file enters a current execution cycle in time according to a previous execution time and an execution cycle of the PHP class file; judging whether the PHP file has a method for relying on the PHP file according to the method for relying on the PHP file;

the execution module 132 is configured to execute, when entering a current execution cycle, a PHP class file without a dependent method;

Further, the execution completion time of the PHP class file is a unix timestamp of a system when the execution of the PHP class file is completed; the completion time recording unit 14 is specifically configured to:

for a PHP type file deployed by a single machine, writing the execution completion time of the PHP type file into a local file of a system;

for a PHP type file deployed by multiple machines, writing the execution completion time of the PHP type file into a mysql database or a distributed application program coordination service zookeeper.

It should be understood that the specific order or hierarchy of steps in the processes disclosed is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not intended to be limited to the specific order or hierarchy presented.

In the foregoing detailed description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, invention lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby expressly incorporated into the detailed description, with each claim standing on its own as a separate preferred embodiment of the invention.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. To those skilled in the art; various modifications to these embodiments will be readily apparent, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean a "non-exclusive or".

Those of skill in the art will further appreciate that the various illustrative logical blocks, units, and steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate the interchangeability of hardware and software, various illustrative components, elements, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.

The various illustrative logical blocks, or elements, described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may be located in a user terminal. In the alternative, the processor and the storage medium may reside in different components in a user terminal.

In one or more exemplary designs, the functions described above in connection with the embodiments of the invention may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media that facilitate transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store program code in the form of instructions or data structures and which can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Additionally, any connection is properly termed a computer-readable medium, and, thus, is included if the software is transmitted from a website, server, or other remote source via a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wirelessly, e.g., infrared, radio, and microwave. Such discs (disk) and disks (disc) include compact disks, laser disks, optical disks, DVDs, floppy disks and blu-ray disks where disks usually reproduce data magnetically, while disks usually reproduce data optically with lasers. Combinations of the above may also be included in the computer-readable medium.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims

1. A PHP timing task management method is characterized by comprising the following steps:

executing the PHP entry file according to a set time period;

2. The PHP timed task management method according to claim 1, wherein executing the PHP entry file according to a set time period comprises:

3. The PHP timed task management method according to claim 2, wherein the comments of the PHP class file execution method include the execution period and the dependent method of the corresponding PHP class file.

4. The PHP timed task management method according to claim 3, wherein executing the PHP class file according to the annotation of the execution method comprises:

5. The PHP timed task management method according to claim 4, wherein the execution completion time of the PHP class file is a unix timestamp of the system when the execution of the PHP class file is completed; after the execution of the PHP class file is completed, recording the execution completion time of the PHP class file, including:

6. A PHP timed task management system, the system comprising:

7. The PHP timed task management system according to claim 6, wherein the entry file execution unit is specifically configured to:

8. The PHP timed task management system according to claim 7, wherein the comments on the PHP class file execution method include the execution period and the dependent method of the corresponding PHP class file.

9. The PHP timed task management system according to claim 8, wherein the class file executing unit includes:

the judgment module is used for judging whether the PHP files enter the current execution cycle in time or not according to the previous execution time and the execution cycle of the PHP files; judging whether the PHP file has a method for relying on the PHP file according to the method for relying on the PHP file;

the execution module is used for executing the PHP class files without a dependent method when entering a current execution cycle;

10. The PHP timed task management system according to claim 9, wherein the execution completion time of the PHP class file is a unix timestamp of the system when the execution of the PHP class file is completed; the completion time recording unit is specifically configured to: