CN111080350A - Software usage amount statistical method and system - Google Patents
Software usage amount statistical method and system Download PDFInfo
- Publication number
- CN111080350A CN111080350A CN201911230113.XA CN201911230113A CN111080350A CN 111080350 A CN111080350 A CN 111080350A CN 201911230113 A CN201911230113 A CN 201911230113A CN 111080350 A CN111080350 A CN 111080350A
- Authority
- CN
- China
- Prior art keywords
- software
- name
- task
- usage
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2462—Approximate or statistical queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
Abstract
The application relates to a software usage amount statistical method and system. The method comprises the following steps: s1, establishing a software list information table based on the pre-recorded common software name information, and establishing a software use record table; s2, acquiring a task related file of a task submitted by a user, and analyzing the task related file to acquire software name information; and S3, comparing the software name information with the software list information table, if the software name information exists in the software list information table, adding a new use record of the corresponding software in the software use record table, if the software name information does not exist in the software list information table, taking the software name information as the new software to be recorded in the software list information table, and simultaneously adding a new use record of the corresponding software in the software use record table. The software list information table is maintained in a preset and automatic supplement combined mode, the use record of software used by a user is recorded under the condition that the user does not sense the software list information table, the use mode is simplified, the management efficiency is improved, and a more convenient, efficient and comprehensive software usage amount counting function can be provided for a system administrator.
Description
Technical Field
The present application relates to software management technologies, and in particular, to a method and a system for counting software usage.
Background
The high-performance computing power is one of key technologies for supporting the continuous development of national strength as the important embodiment of the national comprehensive strength and innovation capability. Currently, high performance computing has been widely used in many fields requiring large-scale scientific computing, such as weather forecasting, oil reservoir exploration, molecular simulation, material design, gene sequencing, and the like.
As an operation management unit of a high-performance computing cluster, a super-computation center needs to collect and master various dimensional data in the running process of the cluster so as to take corresponding measures to provide better service for users, and meanwhile, statistical analysis is carried out on related data so as to provide important support for planning and construction of later-stage clusters. At present, a high-performance computing cluster mainly provides services to the outside, and comprises application scenes of various industries, and used software is five-door, and more importantly, many pieces of software are compiled and installed by a user under a self-account directory of the cluster, so that an existing cluster management system cannot comprehensively obtain a software use list and use amount.
As shown in fig. 1, in the current high-performance cluster system, software usage is mainly counted by setting a software queue, in the method, a separate software queue is set for each type of software, a user designates to submit a job task to the queue when submitting the job task, and then the software usage is counted according to the number of tasks in the queue. The method can realize the statistics of the software use condition which can be called by all users installed in the public directory, but the software names compiled by the users in the own directory cannot be obtained, and the use condition of the software cannot be obtained. Meanwhile, the method needs a cluster administrator to set a queue for each type of software, so that cluster resources are excessively dispersed, the utilization efficiency of the cluster resources is reduced, and the operation and maintenance workload and complexity are increased; too many software queues require manual assignment when the user submits tasks, increasing user complexity. Therefore, the existing method is not suitable for large-scale clusters with numerous application software.
Disclosure of Invention
The technical problem to be solved by the present application is to provide a more convenient, efficient and comprehensive software usage amount statistical method and system for the above defects in the prior art.
In order to solve the technical problem, the present application provides, in a first aspect, a method for counting software usage, including the steps of:
s1, establishing a software list information table based on the pre-recorded common software name information, and establishing a software use record table;
s2, acquiring a task related file of a task submitted by a user, and analyzing the task related file to acquire software name information;
s3, comparing the software name information with the software list information table, if the software name information exists in the software list information table, adding a new use record of corresponding software in the software use record table, if the software name information does not exist in the software list information table, taking the software name information as new software to be recorded in the software list information table, and simultaneously adding a new use record of corresponding software in the software use record table.
In an embodiment according to the first aspect of the present application, the step S2 further includes: and acquiring a task script file of a task submitted by a user, and analyzing the task script file to acquire a preliminary software name.
In an embodiment according to the first aspect of the present application, the step S3 further includes:
s31, comparing the preliminary software name with the software list information table, if yes, adding a new usage record of the corresponding software in the software usage record table, and if not, executing the step S32;
s32, further segmenting the preliminary software name by using a regular expression to obtain an segmented software name;
s33, comparing the segmented software name with the software list information table, if the segmented software name exists, adding a new usage record of the corresponding software in the software usage record table, if the segmented software name does not exist, taking the segmented software name as the new software to be recorded in the software list information table, and simultaneously adding a new usage record of the corresponding software in the software usage record table.
In one embodiment according to the first aspect of the present application, the usage record comprises a task number; the method further comprises the following steps: and analyzing the log file of the corresponding software to acquire the start time and the end time corresponding to the start and the end of the task, and updating the use record corresponding to the task number in the software use record table according to the start time and the end time.
In one embodiment according to the first aspect of the present application, the method further comprises: and querying the software usage record table to obtain the usage statistical information of the required software.
In order to solve the technical problem, the present application provides, in a second aspect, a software usage amount statistics system, including:
the software database module is used for establishing a software list information table based on the pre-recorded common software name information and establishing a software use record table;
the software information acquisition module is used for acquiring a task related file of a task submitted by a user and analyzing the task related file to acquire software name information;
and the statistical management interaction module is used for comparing the software name information with the software list information table, if the software name information exists in the software list information table, adding a new use record of corresponding software in the software use record table, if the software name information does not exist in the software list information table, taking the software name information as new software and inputting the new software into the software list information table, and simultaneously adding a new use record of corresponding software in the software use record table.
In an embodiment of the second aspect of the present application, the software information obtaining module is further configured to obtain a task script file of a task submitted by a user, and parse the task script file to obtain a preliminary software name.
In an embodiment of the second aspect of the present application, the statistics management interaction module is further configured to compare the preliminary software name with the software inventory information table, and if the preliminary software name exists, add a new usage record of the corresponding software in the software usage record table;
the software information acquisition module further divides the preliminary software name by using a regular expression when the preliminary software name does not exist so as to obtain a divided software name;
the statistical management interaction module is further configured to compare the segmented software name with the software inventory information table, if the segmented software name exists, add a new usage record of the corresponding software in the software usage record table, and if the segmented software name does not exist, record the segmented software name as new software into the software inventory information table, and add a new usage record of the corresponding software in the software usage record table.
In one embodiment according to the second aspect of the present application, the usage record comprises a task number; the software information acquisition module also analyzes the log file of the corresponding software to acquire the start time and the end time corresponding to the start and the end of the task; and the statistical management interaction module updates the use record of the corresponding task number in the software use record table by using the starting time and the ending time.
In an embodiment according to the second aspect of the present application, the statistics management interaction module is further configured to query the software usage record table to obtain usage statistics information of the required software.
According to the software usage amount statistical method and the system, the software list information table and the software usage record table are established, the software list information table is maintained in a preset and automatic supplement combined mode, the fact that a user records names, times, duration and other related data of all application software used by cluster operation of the user under the condition of no perception is achieved, an independent task queue is not needed to be set according to software, the use mode is simplified, the management efficiency is improved, and a more convenient, efficient and comprehensive cluster software usage amount statistical function is provided for a system administrator.
Drawings
The present application will be further described with reference to the accompanying drawings and examples, in which:
FIG. 1 is a diagram illustrating a prior art method for setting a software queue to count software usage;
FIG. 2 is a block diagram of the logical structure of a software usage statistics system according to an embodiment of the present application;
FIG. 3 is a block diagram of a logical structure of a software information acquisition module in an embodiment of the present application;
FIG. 4 is a block diagram of a logical structure of a statistics management interaction module in one embodiment of the present application;
FIG. 5 is a flow chart of a software usage statistics method according to one embodiment of the present application;
fig. 6 is a flowchart of a software usage statistics method according to another embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. Also, the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
FIG. 2 shows a block diagram of a logical structure of a software usage statistics system according to one embodiment of the present application. As shown in fig. 2, the software usage amount statistical system includes a software database module 110, a statistics management interaction module 120, and a software information acquisition module 130. The software database module 110 is mainly used for establishing a software list information table based on pre-recorded common software name information and establishing a software use record table; the software information obtaining module 130 is configured to obtain a task related file of a task submitted by a user, and parse the task related file to obtain software name information; the statistics management interaction module 120 is configured to compare the software name information acquired by the software information acquisition module 130 with the software inventory information table established by the software database module 110. If the software list information table has the software name information, the statistics management interaction module 120 adds a new usage record of the corresponding software in the software usage record table. If the software name information does not exist in the software list information table, the statistical management interaction module 120 records the software name information as new software into the software list information table, and simultaneously adds a new usage record corresponding to the software in the software usage record table.
In an embodiment, the system administrator may pre-enter information of names of various common applications through the statistics management interaction module 120 and store the information into the software database module 110 to form the aforementioned software inventory information table. The system administrator can also perform maintenance modification on the stored software name information in the software inventory information table through the statistics management interaction module 120. Meanwhile, a software usage record table is also established in the software database module 110. The software information obtaining module 130 further includes a file parsing module 131 and a text segmentation module 132, as shown in fig. 3. Statistics management interaction module 120 further includes a software information maintenance module 121 and a retrieve statistics module 122. The software information obtaining module 130 is automatically triggered based on the task submitted by the user, and obtains a task related file, such as a task script file, of the task submitted by the user. Then, the file parsing module 131 parses the task script file of the submitted task through a text parsing function, and obtains a preliminary software name. The software information maintenance module 121 compares the preliminary software name parsed by the text parsing module 131 with a preset software information list in the software list information table. If the preliminary software name exists in the software list information table, the software information maintenance module 121 adds a new usage record corresponding to the software in the software usage record table, where the usage record may include information such as the software name, the task number, the user number, and the submission time. If the preliminary software name does not exist in the software list information table, the text word segmentation module 132 further segments the preliminary software name by using a regular expression, for example, the tail (number, decimal point, underline, and horizontal line) of the parsed preliminary software name is removed, so as to obtain the segmented software name. Then, the software information maintenance module 121 compares the segmented software name with the software list information table. If the segmented software name exists in the software list information table, the software information maintenance module 121 adds a new usage record corresponding to the software in the software usage record table. If the software list information table does not have the split software name, the software information maintenance module 121 records the split software name as new software into the software list information table, and adds a new usage record corresponding to the software in the software usage record table. Therefore, by establishing the software list information table and the software use record table and maintaining the software list information table in a mode of combining preset and automatic supplement, the user can record the use record related data of all application software used by the user for submitting the task under the condition of no perception, an independent task queue does not need to be set according to the software, the use mode is simplified, and the management efficiency is improved.
Further, the software information maintenance module 121 may also automatically update the software usage record table after the task starts to be calculated, so as to increase the software usage record starting time; after the task is finished (normal completion, abnormal exit, manual termination and the like), the software use record table is automatically updated, and the software use record finishing time is increased. For example, the software information obtaining module 130 may further obtain a log file of the corresponding software, analyze the log file by the file analyzing module 131, obtain a start time and an end time corresponding to the start and the end of the task, provide the start time and the end time to the software information maintaining module 121, update the usage record corresponding to the task number in the software usage record table by the software information maintaining module 121, and record the start time and the end time of the corresponding task in the software usage record table.
Further, the retrieval statistics module 122 is used for retrieving the query software usage record table to obtain the usage statistics information of the required software. For example, the retrieval statistics module 122 provides multidimensional query and statistics functions according to task start and stop time, user number, task number, software name, and the like, and a system administrator can obtain required software usage statistics information by self through the retrieval statistics module 122, and form a statistics report, thereby facilitating guidance of operation management and service planning.
The following describes in detail a workflow of the software usage amount statistics system according to the specific embodiment of the present application, taking lsf (load sharing facility) scheduling software used by a high-performance computing cluster as an example. When a cluster user submits a task through the LSF, log information records information of a submission node, a submission directory, a script file and the like of the task, and the system acquires the task script file through the software information acquisition module 130 and reads the content of the task script file. The contents of the common LSF script file are classified into the following three types:
script type 1: the software executable path is directly unloaded into the RUN variable.
APP_NAME＝AMD_small
NP＝8
NP_PER_NODE＝4
RUN＝"/home-fn/Soft/ansys_inc/v140/fluent/fluent14.0.0/bin/fluent-r14.0.0 3d-g-i fluent elbow.jou"
Script type 2: the RUN variable value is RAW, and the path of the software executable file is specified in a line head mode in other lines below.
APP_NAME＝AMD_small
NP＝8
NP_PER_NODE＝4
RUN＝"RAW"
/home-fn/Soft/ansys_inc/v140/fluent/fluent14.0.0/bin/fluent-r14.0.03d-g-i fluent elbow.jou
Script type 3: the RUN variable is RAW, and the path of the software executable is specified in other lines below and not at the head of the line.
Aiming at the various scripts, the software information acquisition module firstly acquires a task script file corresponding to the task according to the LSF script and reads the content, and the task script file is executed according to the following flow:
(1) using a file parsing module to search a file containing "RUN ═ and no" #!after the space is removed from the head of the line! "in the text line.
(2) It is determined whether the line content is "RUN ═ RAW".
2.1) if not, the description is a first type script file, the software executable file is directly written into the RUN variable, and the software name is obtained by using the text word segmentation module, which is specifically as follows: dividing RUN value content by taking a blank space as a separator; for the first element obtained after segmentation, segmenting the content by taking '/' as a separator; and taking the last element after segmentation as a preliminary software name.
2.2) if yes, utilizing a file resolving module to resolve whether the content of the "mpirun" or the "mpiexec" is contained or not, and the space is removed from the head of the line and then the "#! "in the text line.
2.2a) if present, the description is of a third type of script file. The software name is obtained by using a text word segmentation module, which comprises the following specific steps: dividing the line content by taking mpirun or mpixec as a separator to obtain a first element containing a "/" symbol; segmenting the content by taking the element value as a delimiter, "/"; and taking the last element after segmentation as a preliminary software name.
2.2b) if not, the description is a second type script file. Obtaining a text line which is started by a '/' after a line head is removed from a space by using a file analysis module; and dividing the RUN value content by taking a blank space as a separator. Aiming at the first element obtained after segmentation, analyzing whether the corresponding file is an executable file or not by using a shell script, and if so, segmenting the content by taking a '/' as a separator; taking the last element after segmentation as a preliminary software name; if not, acquiring a next text line starting with the "/", repeating the step until the corresponding file is an executable file, and segmenting the content by taking the "/" as a separator; and taking the last element after segmentation as a preliminary software name.
(3) And (3) utilizing a statistic management interaction module to perform traversal retrieval on the preliminary software name obtained in the step (2) in a software list information table, if the preliminary software name exists, executing the step (4), and otherwise, executing the step (5).
(4) And newly adding a use record corresponding to the software in the software use record table according to the preliminary software name, wherein the use record comprises information such as the software name, the task number, the user number, the submission time and the like.
(5) And further segmenting the obtained preliminary software name by using a text word segmentation module, removing the tail part by using a regular expression, removing the contents such as numbers, decimal points, underlines, short transverse lines and the like contained after letters are removed, and obtaining the segmented software name. And then, traversing and searching the segmented software name in a software list information table by using a statistic management interaction module, if the segmented software name exists, executing the step (4), and if the segmented software name does not exist, executing the step (6).
(6) And (4) taking the segmented software name obtained in the step (5) as new software, newly adding a software record in a software list information table, and simultaneously newly adding a use record of corresponding software in a software use record table, wherein the use record comprises information such as the software name, the task number, the user number, the submission time and the like.
(7) And analyzing the LSF log information by using a software information acquisition module, updating the use record of the corresponding task number in a software use record table through a statistical management interaction module when the task state changes into the start or the end of operation, and modifying the information such as the start time and the end time of the task.
(8) A system administrator maintains the software list information table through the statistic management interaction module, and can comprehensively inquire the software usage record table through fields such as software name, user number, task number, start time, end time and the like to obtain the software usage condition and form a statistic report.
Aiming at different high-performance computing clusters, scheduling management software adopted by the high-performance computing clusters can be other software such as PBS (packet switched service) and Maui (Maui) besides LSF (least Square), the formats of task script files corresponding to different software are different, but the realization of a software usage amount statistical system provided by the application is not influenced, because only the system codes of the software information acquisition module need to be modified according to the application aiming at the corresponding software, and the functions of other modules can be universal.
Based on the software usage amount statistical system introduced in combination with the various embodiments of the present application, the present application also provides a software usage amount statistical method. FIG. 5 shows a flow diagram of a software usage statistics method according to one embodiment of the present application. As shown in fig. 5, the software usage amount statistical method includes the following steps:
in step S210, a software list information table is established based on the pre-entered common software name information, and a software usage record table is established;
in step S220, a task related file of a task submitted by a user is acquired, and the task related file is analyzed to acquire software name information;
in step S230, the software name information is compared with the software list information table, if the software name information exists, a usage record of the corresponding software is newly added in the software usage record table, and if the software name information does not exist, the software name information is recorded in the software list information table as the new software, and meanwhile, a usage record of the corresponding software is newly added in the software usage record table.
FIG. 6 is a flow chart illustrating a method for software usage statistics according to another embodiment of the present application. As shown in fig. 6, the method includes the steps of:
in step S310, a software list information table is established based on the common software name information entered in advance, and a software usage record table is established. A system administrator can pre-input various common application software name information through the statistical management interaction module and store the common application software name information into the software database module to form the software list information table, and meanwhile, a software use record table is established in the software database module.
Then, in step S320, a task script file of a task submitted by a user is obtained, and the task script file is parsed to obtain a preliminary software name.
Then, in step S330, the preliminary software name is compared with the software list information table, if the preliminary software name exists in the software list information table, step S340 is executed, and if the preliminary software name does not exist, step S350 is executed.
In step S340, a new usage record corresponding to the software is added to the software usage record table, where the usage record may include information such as a software name, a task number, a user number, and a submission time.
In step S350, the preliminary software name is further segmented by using a regular expression to obtain a segmented software name.
Then, in step S360, the split software name is compared with the software list information table, if the split software name exists in the software list information table, the step S340 is executed, and if the split software name does not exist, the step S370 is executed.
In step S370, the segmented software name is recorded as new software into the software inventory information table, and a usage record of the corresponding software is newly added to the software usage record table, where the usage record may include information such as software name, task number, user number, and submission time.
According to the software usage amount statistical method, the software list information table and the software usage record table are established, the software list information table is maintained in a preset and automatic supplement combined mode, the usage record related data of all application software used by a user for submitting a task are recorded under the condition that the user does not sense, an independent task queue does not need to be set according to software, the usage mode is simplified, and the management efficiency is improved.
Further, the software usage amount statistical method further comprises analyzing log files of corresponding software to obtain start time and end time corresponding to the start and the end of the task, and updating the usage record of the corresponding task number in the software usage record table according to the start time and the end time. Further, the software usage statistical method further comprises querying the software usage record table to obtain usage statistical information of the required software. Therefore, a system administrator can comprehensively inquire the software usage record table through fields such as software names, user numbers, task numbers, start time, end time and the like, obtain the software usage condition and form a statistical report.
The software usage amount statistical method and the system according to the embodiment of the application have the following advantages: 1) high-performance clusters of various scales can be effectively used without independently setting corresponding queues for each type of software; 2) the problem of high-performance resource segmentation caused by the arrangement of the queue and the trouble of selecting the queue when a user submits a task are avoided; 3) software conditions of all tasks in the cluster can be counted, whether the software is public software of a shared directory or software compiled by individuals in a user directory; 4) a software analysis mode combining software presetting and automatic supplementation is provided, the task software information acquisition efficiency is improved, and meanwhile, the accuracy of software information is improved; 5) the multidimensional information storage and retrieval such as software use information names, start-stop time, task numbers, user numbers and the like are provided, and a more convenient, efficient and comprehensive cluster software use amount counting function is provided for a system administrator.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (10)
1. A statistical method for software usage is characterized by comprising the following steps:
s1, establishing a software list information table based on the pre-recorded common software name information, and establishing a software use record table;
s2, acquiring a task related file of a task submitted by a user, and analyzing the task related file to acquire software name information;
s3, comparing the software name information with the software list information table, if the software name information exists in the software list information table, adding a new use record of corresponding software in the software use record table, if the software name information does not exist in the software list information table, taking the software name information as new software to be recorded in the software list information table, and simultaneously adding a new use record of corresponding software in the software use record table.
2. The method for counting software usage according to claim 1, wherein said step S2 further comprises: and acquiring a task script file of a task submitted by a user, and analyzing the task script file to acquire a preliminary software name.
3. The method for counting software usage according to claim 2, wherein said step S3 further comprises:
s31, comparing the preliminary software name with the software list information table, if yes, adding a new usage record of the corresponding software in the software usage record table, and if not, executing the step S32;
s32, further segmenting the preliminary software name by using a regular expression to obtain an segmented software name;
s33, comparing the segmented software name with the software list information table, if the segmented software name exists, adding a new usage record of the corresponding software in the software usage record table, if the segmented software name does not exist, taking the segmented software name as the new software to be recorded in the software list information table, and simultaneously adding a new usage record of the corresponding software in the software usage record table.
4. The software usage statistics method of claim 1, wherein the usage record contains a task number; the method further comprises the following steps: and analyzing the log file of the corresponding software to acquire the start time and the end time corresponding to the start and the end of the task, and updating the use record corresponding to the task number in the software use record table according to the start time and the end time.
5. The software usage statistics method of claim 1, wherein the method further comprises: and querying the software usage record table to obtain the usage statistical information of the required software.
6. A software usage statistics system, comprising:
the software database module is used for establishing a software list information table based on the pre-recorded common software name information and establishing a software use record table;
the software information acquisition module is used for acquiring a task related file of a task submitted by a user and analyzing the task related file to acquire software name information;
and the statistical management interaction module is used for comparing the software name information with the software list information table, if the software name information exists in the software list information table, adding a new use record of corresponding software in the software use record table, if the software name information does not exist in the software list information table, taking the software name information as new software and inputting the new software into the software list information table, and simultaneously adding a new use record of corresponding software in the software use record table.
7. The system of claim 6, wherein the software information obtaining module is further configured to obtain a task script file of a task submitted by a user, and parse the task script file to obtain a preliminary software name.
8. The system according to claim 7, wherein the statistics management interaction module is further configured to compare the preliminary software name with the software inventory information table, and if the preliminary software name exists, add a new usage record of the corresponding software in the software usage record table;
the software information acquisition module further divides the preliminary software name by using a regular expression when the preliminary software name does not exist so as to obtain a divided software name;
the statistical management interaction module is further configured to compare the segmented software name with the software inventory information table, if the segmented software name exists, add a new usage record of the corresponding software in the software usage record table, and if the segmented software name does not exist, record the segmented software name as new software into the software inventory information table, and add a new usage record of the corresponding software in the software usage record table.
9. The software usage statistics system of claim 5, wherein the usage record contains a task number; the software information acquisition module also analyzes the log file of the corresponding software to acquire the start time and the end time corresponding to the start and the end of the task; and the statistical management interaction module updates the use record of the corresponding task number in the software use record table by using the starting time and the ending time.
10. The system of claim 5, wherein the statistics management interaction module is further configured to query the software usage record table to obtain usage statistics information of the required software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911230113.XA CN111080350A (en) | 2019-12-04 | 2019-12-04 | Software usage amount statistical method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911230113.XA CN111080350A (en) | 2019-12-04 | 2019-12-04 | Software usage amount statistical method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111080350A true CN111080350A (en) | 2020-04-28 |
Family
ID=70312889
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911230113.XA Pending CN111080350A (en) | 2019-12-04 | 2019-12-04 | Software usage amount statistical method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111080350A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1852538A (en) * | 2005-10-25 | 2006-10-25 | 华为技术有限公司 | Method and apparatus for monitoring and updating software in apparatus management |
| CN101916415A (en) * | 2010-08-06 | 2010-12-15 | 西北工业大学 | On-demand service method for software license in cloud computing platform |
| US20100325149A1 (en) * | 2009-06-22 | 2010-12-23 | Craig Stephen Etchegoyen | System and Method for Auditing Software Usage |
-
2019
- 2019-12-04 CN CN201911230113.XA patent/CN111080350A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1852538A (en) * | 2005-10-25 | 2006-10-25 | 华为技术有限公司 | Method and apparatus for monitoring and updating software in apparatus management |
| US20100325149A1 (en) * | 2009-06-22 | 2010-12-23 | Craig Stephen Etchegoyen | System and Method for Auditing Software Usage |
| CN101916415A (en) * | 2010-08-06 | 2010-12-15 | 西北工业大学 | On-demand service method for software license in cloud computing platform |
Non-Patent Citations (1)
| Title |
|---|
| 玉树临风: "深圳超算HPC使用手册v3.1", pages 24 - 29, Retrieved from the Internet <URL:https://www.docin.com/p-1032516682.html> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106326429A (en) | Hbase second-level query scheme based on solr | |
| CN109669925B (en) | Management method and device of unstructured data | |
| CN109885642B (en) | Hierarchical storage method and device for full-text retrieval | |
| CN111562885A (en) | Data processing method and device, computer equipment and storage medium | |
| CN110245134B (en) | Increment synchronization method applied to search service | |
| CN114077602B (en) | Data migration method and device, electronic equipment and storage medium | |
| CN111008521A (en) | Method and device for generating wide table and computer storage medium | |
| CN114116762A (en) | Offline data fuzzy search method, device, equipment and medium | |
| CN113177090A (en) | Data processing method and device | |
| CN111666344A (en) | Heterogeneous data synchronization method and device | |
| CN113849499A (en) | Data query method and device, storage medium and electronic device | |
| CN111026709A (en) | Data processing method and device based on cluster access | |
| CN107291938A (en) | Order Query System and method | |
| CN113568931A (en) | Route analysis system and method for data access request | |
| CN111080350A (en) | Software usage amount statistical method and system | |
| CN113590651B (en) | HQL-based cross-cluster data processing system and method | |
| CN114385551B (en) | Log time-sharing management method, device, equipment and storage medium | |
| CN115033646A (en) | Method for constructing real-time warehouse system based on Flink and Doris | |
| CN109902067B (en) | File processing method and device, storage medium and computer equipment | |
| CN111488327B (en) | Data standard management method and system | |
| CN113760907A (en) | Data uniqueness identification method in database | |
| Jiadi et al. | Research on Data Center Operation and Maintenance Management Based on Big Data | |
| CN110955710A (en) | Method and device for processing dirty data in data exchange operation | |
| CN111563123A (en) | Live warehouse metadata real-time synchronization method | |
| KR101638048B1 (en) | Sql query processing method using mapreduce |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |