CN104035938A - Performance continuous integration data processing method and device - Google Patents
Performance continuous integration data processing method and device Download PDFInfo
- Publication number
- CN104035938A CN104035938A CN201310072553.3A CN201310072553A CN104035938A CN 104035938 A CN104035938 A CN 104035938A CN 201310072553 A CN201310072553 A CN 201310072553A CN 104035938 A CN104035938 A CN 104035938A
- Authority
- CN
- China
- Prior art keywords
- performance
- integration
- continues
- achievement data
- integration testing
- 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
Classifications
-
- 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/2455—Query execution
- G06F16/24552—Database cache management
-
- 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/21—Design, administration or maintenance of databases
- G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0608—Saving storage space on storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
Abstract
The invention provides a performance continuous integration data processing method and device. The method includes acquiring a performance continuous integration test result document stored in a disk, wherein the performance continuous integration test result document comprises a plurality of performance continuous integration test records; reading the plurality of performance continuous integration test records into a memory one by one; analyzing the performance continuous integration test records in the memory to obtain corresponding middle performance index data; deleting the analyzed performance continuous integration test records in the memory; judging whether analyzing of the plurality of performance continuous integration test records in the performance continuous integration test result document is completed; if analyzing of the plurality of performance continuous integration test records in the performance continuous integration test result document is completed, acquiring final performance index data and deleting the performance continuous integration test result document in the disk; storing the final performance index data to the memory and the disk. According to the performance continuous integration data processing method and device, space usage of the disk can be reduced, and analyzing and reading efficiency of regression result data is improved.
Description
Technical field
The application relates to the technical field of performance test, particularly relates to the method for the lasting integrated data processing of a kind of performance, and a kind of performance continues the device of integrated data processing.
Background technology
Performance is lasting integrated is to trigger based on some conditions after (as clocked flip, manual triggering or trunk code change i.e. triggering etc.), constantly collecting performance index, and data are made to a process of resolving.By defining and control after suitable trigger condition, just can collect performance index as lasting integrated result, this wherein mainly comprises response time (Response Time, be called for short RT), handling capacity (successful number of transactions per second, be called for short TPS) and the data such as integrated state, it can find the performance issue causing because of the change of some condition in time.
Jmeter is the project of increasing income of a pure Java on the Apache foundation Jakarta based on java language, as the performance test instrument of exerting pressure, has widely applied in the performance test process of each company at present, such as google etc.In Jmeter when operation, generates multiple threads and simulates multiple users and carry out request, and the information such as the response time, request initiation time, request results of request have all been recorded in each request, and the destination file of generation is that suffix is the xml formatted file of .jtl.So this file have file large, record the characteristics such as number is many.
Hudson is the Open Framework of a lasting integrating engine, it need to define some trigger conditions just can support the lasting structure based on task, and Hudson has a set of oneself developing plug specification, and continue at present the performance plug-in unit Performance Plugin that increases income that has of integrated (continuing integrated) based on performance.
With reference to the Performance Plugin plug-in unit workflow diagram shown in figure 1, after task is triggered by Hudson, Hudson can distribute an idle machine to this task.Performance Plugin plug-in unit just can be at this machine deploy Jmeter, and execution continues integration servers on this machine, task finishes rear generation .jtl file, and by .jtl file copy to Hudson machine, resolved by Performance plugin.When parsing, because .jtl file is a rule record, original plug-in unit can all be written into internal memory by it, and resolves, and finally obtains performance index.And storage. destination file, in order to regression result inquiry.
But the implementation of above-mentioned Performance Plugin plug-in unit has the following disadvantages:
(1) destination file of Jmeter is stored on disk, and suffix is .jtl file, and it has recorded the result of each request.In actual recurrence scene, once returning working time is 10～15 minutes, I haven't seen you for ages produces ten thousand records of 9-20 for the .jtl file generating, and in the time that TPS reaches 5000, return scene and can produce 2,400,000 records, the mean size of every record is 200b, once can produce the data of nearly 300M.Be to carry out once minimum every day and return scene, most historic task builds and has exceeded 100 times, and 1 task just at least needs 29G disk space so.If recurrence task constantly increases, will need a large amount of disk spaces.
(2) regression result data statistics displaying.When Performance-Plugin plug-in unit is checked historical or current regression result at every turn, all records in .jtl file all can be written into internal memory, and resolve.A regression result Data Analysis need to be written into 300M data, the analysis result of getting so 10 structure information just needs the memory headroom of nearly 3G, not only can cause JVM(Java virtual machine) constantly carry out frequently garbage reclamation, the risk that even there will be internal memory to overflow.In actual scene, once find, resolve a recurrence task that builds number of times 15, or resolve together while exceeding 5 recurrence tasks, will directly cause Hudson that service cannot be provided.
Therefore, those skilled in the art's problem in the urgent need to address is: the treatment mechanism that provides a kind of performance to continue integrated data, use in order to the space of reducing disk, and improve parsing and the reading efficiency of regression result data.
Summary of the invention
Technical problems to be solved in this application are to provide the method for the lasting integrated data processing of a kind of performance, in order in the space use of carrying out reducing in the lasting integrated process of performance disk, improve parsing and the reading efficiency of regression result data.
Accordingly, the device that the application also provides a kind of performance to continue integrated data processing, in order to ensure said method application in practice.
In order to address the above problem, the application discloses the method for the lasting integrated data processing of a kind of performance, comprising:
Obtain the performance being stored in disk and continue integration testing destination file, described performance continues integration testing destination file and comprises that many performances continue integration testing record;
Described many performances are continued to integration testing record to be read in internal memory one by one;
Performance in described internal memory is continued to integration testing record and resolve, obtain corresponding intermediate performance achievement data;
The performance being parsed described in deleting in internal memory continues integration testing record;
Judge whether the lasting integration testing record of many performances that described performance continues in integration testing destination file is parsed;
If so, obtain final performance achievement data, and the performance of deleting in disk continues integration testing destination file;
Described final performance achievement data is stored in internal memory and disk.
Preferably, the step of obtaining the lasting integration testing destination file of performance being stored in disk described in comprises:
In the time meeting the trigger condition of the lasting integration servers of performance, carry out described performance and continue integration servers;
The sub-step that described execution performance continues integration servers further comprises:
Initiate performance and continue integration testing request;
Continue integration testing request according to described performance described performance is continued to the lasting integration testing of integration servers execution performance, obtain performance and continue integration testing record;
Store described performance and continue the lasting integration testing destination file of integration testing record generation performance.
Preferably, describedly performance in internal memory is continued to integration testing record resolve, the step that obtains corresponding intermediate performance achievement data comprises:
Described many performances are continued to integration testing record to be read in the buffer queue arranging in internal memory one by one;
From described buffer queue, read one by one described performance and continue integration testing record, calculate intermediate performance achievement data according to default statistical rules;
Describedly judge that performance continues many performances in integration testing destination file and continues integration testing and record the step whether being parsed and comprise:
Judge that described performance continues integration testing record and whether comprises default end mark;
If so, the lasting integration testing record of many performances being judged as in the lasting integration testing destination file of described performance is parsed.
Preferably, described final performance achievement data is that the lasting integration testing of performance that comprises default end mark records corresponding intermediate performance achievement data.
Preferably, the described step that final performance achievement data is stored in internal memory and disk comprises:
Obtain the performance corresponding with described final performance achievement data and continue integration servers title and/or the lasting integration servers numbering of performance;
The mapping relations that described final performance achievement data, final performance achievement data and described performance continued to integration servers title and/or the lasting integration servers numbering of performance are stored in internal memory and disk.
Preferably, described method also comprises:
From internal memory or disk, read described final performance achievement data.
Preferably, the described step that reads final performance achievement data from internal memory or disk comprises:
Receptivity achievement data inquiry request, the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
In internal memory, search described performance and continue integration servers title and/or the lasting integration servers numbering of performance;
If search successfully, obtain with the lasting integration servers title of described performance and/or performance and continue final performance achievement data corresponding to integration servers numbering and return;
If search unsuccessfully, continue integration servers title and/or the lasting integration servers numbering of performance spanned file path according to described performance; In disk, read described final performance achievement data according to described file path.
Preferably, the described step that reads final performance achievement data from internal memory or disk comprises:
Receive the performance index data query request that external system sends, the request of described performance index data query comprises that performance continues integration servers title, and performance continues integration servers numbering;
Continue the link data of integration servers title and/or the default form of performance lasting integration servers numbering generation and return according to described performance;
Receive the links and accesses of external system, from internal memory or disk, obtain final performance achievement data and return according to described links and accesses.
Disclosed herein as well is the device that a kind of performance continues integrated data processing, comprising:
File acquisition module, the performance that is stored in disk for obtaining continues integration testing destination file, and described performance continues integration testing destination file and comprises that many performances continue integration testing record;
Record insmods, and reads to one by one internal memory for described many performances being continued to integration testing record;
Record parsing module, resolve for the performance of described internal memory being continued to integration testing record, obtain corresponding intermediate performance achievement data;
Record removing module, for continuing integration testing record in the performance being parsed described in internal memory deletion;
Judge module, for judging that many performances of the lasting integration testing destination file of described performance continue integration testing record and whether are parsed; If so, call final performance achievement data and obtain module;
Final performance achievement data obtains module, for obtaining final performance achievement data;
File removing module, continues integration testing destination file for the performance of deleting disk;
Final performance achievement data memory module, for being stored to internal memory and disk by described final performance achievement data.
Preferably, described file acquisition module comprises following submodule:
Tasks carrying submodule, in the time meeting the trigger condition of the lasting integration servers of performance, carries out described performance and continues integration servers;
Described tasks carrying submodule further comprises with lower unit:
Request initiating cell, continues integration testing request for initiating performance;
Record acquiring unit, for continue integration testing request according to described performance, described performance is continued to the lasting integration testing of integration servers execution performance, obtain performance and continue integration testing record;
File generating unit, continues the lasting integration testing destination file of integration testing record generation performance for storing described performance.
Preferably, the described parsing module that records comprises following submodule:
Buffer queue is put into submodule, reads to one by one in the buffer queue arranging at internal memory for described many performances being continued to integration testing record;
Intermediate performance achievement data calculating sub module, continues integration testing record for read one by one described performance from described buffer queue, calculates intermediate performance achievement data according to default statistical rules;
Described judge module comprises following submodule:
Default end mark judges submodule, for judging that described performance continues integration testing record and whether comprises default end mark; If so, call and be parsed judgement submodule;
Be parsed judgement submodule, many performances that continue integration testing destination file for being judged as described performance continue integration testing record and are parsed.
Preferably, described final performance achievement data is that the lasting integration testing of performance that comprises default end mark records corresponding intermediate performance achievement data.
Preferably, described final performance achievement data memory module comprises:
Performance continues integration servers acquisition of information submodule, and for obtaining, the performance corresponding with described final performance achievement data continues integration servers title and/or performance continues integration servers numbering;
Sub module stored, is stored to internal memory and disk for the mapping relations that described final performance achievement data, final performance achievement data and described performance continued to integration servers title and/or the lasting integration servers numbering of performance.
Preferably, described device also comprises:
Final performance achievement data read module, for reading described final performance achievement data from internal memory or disk.
Preferably, described final performance achievement data read module comprises following submodule:
Request receiving submodule, for receptivity achievement data inquiry request, the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
Search submodule, for searching at internal memory, described performance continues integration servers title and/or performance continues integration servers numbering;
Return to submodule, while searching successfully for continue the lasting integration servers numbering of integration servers title and/or performance in described performance, obtain with the lasting integration servers title of described performance and/or performance and continue final performance achievement data corresponding to integration servers numbering and return;
File path generation submodule, while searching unsuccessfully, continues integration servers according to the lasting integration servers title of described performance and/or performance and numbers spanned file path for continue the lasting integration servers numbering of integration servers title and/or performance in described performance; In disk, read described final performance achievement data according to described file path.
Preferably, described final performance achievement data read module comprises following submodule:
External system inquiry request receives submodule, the performance index data query request sending for receiving external system, and the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
Link data generates submodule, generates the link data of default form and returns for continue the lasting integration servers numbering of integration servers title and/or performance according to described performance;
Performance index data are returned to submodule, for receiving the links and accesses of external system, obtain final performance achievement data and return according to described links and accesses from internal memory or disk.
Compared with prior art, the application has the following advantages:
(1) space of minimizing disk is used.Generating after the lasting integration testing destination file of performance, just it is resolved, performance is continued to the lasting integration testing record of every row performance in integration testing destination file and add up, output intermediate performance achievement data (comprises average response time, response time distributes, tps etc.).Many performances that continue in integration testing destination file in performance continue after integration testing record is parsed to generate final performance achievement data, delete original performance and continue integration testing destination file, and described final performance achievement data is kept in disk and internal memory.Like this, the final performance achievement data size after statistics only has 2kb left and right, has saved the space of disk and internal memory far away.
(2) improve performance and continue the analyzing efficiency that integration testing records, discharge the pressure to internal memory.In order to prevent that huge performance is continued to integration testing destination file is written into internal memory, and cause low memory, the application adopts a buffer queue, performance is continued to integration testing record reads in buffer queue one by one, and there is a computational threads to record and calculate from the lasting integration testing of queue taking-up performance specially, obtain performance index data, calculated the performance of all deleting in internal memory at every turn and continued integration testing record, ensure its not committed memory space.Adopt after such pattern the performance index data that only need the memory headroom buffer memory of 4k left and right to calculate.
(3) quick obtaining performance index data.During for fear of inquiry integrated data, analysis feature continues integration testing destination file again, continues crucial performance index data in integration testing record except using computational threads to extract performance, also these performance index data is stored in disk.Even if Hudson application is restarted like this, also can from disk, read the performance index data of having added up.Adopt after this kind of scheme, the delay probability of machine of Hudson greatly reduces.
(4) also creationary open performance achievement data of the application, offers external system access in URL mode, and external system docking application just can easily be obtained task and be built information like this.
Brief description of the drawings
Fig. 1 is the Performance Plugin plug-in unit workflow diagram in the application's background technology;
Fig. 2 is the flow chart of steps that a kind of performance of the application continues the embodiment of the method for integrated data storage;
Fig. 3 is the flow chart of steps that a kind of performance of the application continues the embodiment of the method 1 that reads of integrated data;
Fig. 4 is the flow chart of steps that a kind of performance of the application continues the embodiment of the method 2 that reads of integrated data;
Fig. 5 is the structured flowchart that a kind of performance of the application continues the device embodiment of integrated data storage.
Embodiment
For the above-mentioned purpose, the feature and advantage that make the application can become apparent more, below in conjunction with the drawings and specific embodiments, the application is described in further detail.
One of core idea of the embodiment of the present application is, continue integration testing destination file while resolving obtaining performance, one by one described performance is continued to integration testing record and be written in the buffer queue of internal memory, and be provided with computational threads and from queue, take out performance and continue integration testing record and generate and after performance achievement data completes, from internal memory, remove this performance and continue integration testing record.After the lasting integration testing record of all performances is all parsed, to delete original performance and continue integration testing destination file, computational threads generates a final performance achievement data, and is stored in internal memory and disk.
The processing procedure that a kind of performance of the application continues integrated data disposal route and device comprises that performance continues the process of integrated data storage and the process that the lasting integrated data of performance reads, and following examples describe with regard to process and the process that reads of the lasting integrated data storage of performance respectively.
With reference to Fig. 2, show the flow chart of steps of the embodiment of the method for the lasting integrated data storage of a kind of performance, in the embodiment of the present application, the storage means that continues integrated data taking the performance based on Hudson, as example describes, specifically can comprise the following steps:
Step 101, obtains the performance being stored in disk and continues integration testing destination file, and described performance continues integration testing destination file and comprises that many performances continue integration testing record;
Particularly, continuing integrated is a kind of practice of software, wherein often integrated their work of the member of team, conventionally everyone is at least once integrated every day, this just causes the every day can be repeatedly integrated, each integrated be that structure (comprising test) by robotization carries out, object is to allow team receive and feed back and improve on lasting basis, and needn't wait until that later stage construction cycle just finds and repair-deficiency; Performance continues, and integrated (also can be called performance returns) is after triggering based on some conditions, constantly collects performance index data, and described performance index data made to the process of resolving.
In specific implementation, Hudson is the Open Framework of a lasting integrating engine, only need to define some trigger conditions, and it just can support the lasting structure based on task.
In a preferred embodiment of the present application, described step 101 can comprise following sub-step:
Sub-step S11, in the time meeting the trigger condition of the lasting integration servers of performance, carries out described performance and continues integration servers;
Particularly, Hudson has a set of oneself developing plug specification, and continues the integrated plug-in unit Performance Plugin that increases income that has based on performance at present.In the time meeting the trigger condition of the lasting integration servers of performance, the performance of specifying continues integration servers and can be triggered by Hudson, then Hudson distributes an idle machine to continue integration servers to the performance of described appointment, and Performance Plugin plug-in unit just can be carried out described performance and continue integration servers on this machine.
In practice, the trigger condition that described performance continues integration servers can be clocked flip condition, trigger performance by timer mechanism and continue integration servers, such as be a timer of the lasting integration servers configuration of each performance in Hudson, as * * * 30?, it represents that every day, 3:00 triggered the lasting integration servers of the performance of specifying; Certainly, described performance continues the trigger condition of integration servers can also comprise that code changes trigger condition, manual trigger on interface etc., the application to this without being limited.
In a preferred embodiment of the present application, the sub-step that described execution performance continues integration servers further can comprise following sub-step:
Sub-step S111, initiates performance and continues integration testing request;
Sub-step S112, continues integration testing request according to described performance described performance is continued to the lasting integration testing of integration servers execution performance, obtains performance and continues integration testing record;
In specific implementation, Performance Plugin is at machine deploy Jmeter instrument, continue integration testing for the performance that described performance is continued to integration servers, wherein, Jmeter is the project of increasing income of a pure Java on the Apache foundation Jakarta based on java language, can be for to resource (file static state and dynamic, Servlet, perl script, java object, database and inquiry, ftp server etc.) performance test, as the performance test instrument of exerting pressure, in Jmeter when operation, generates multiple threads and simulates multiple users and carry out request, each request can obtain performance and continue integration testing record.Described performance continues integration testing record and can be expressed as follows:
<httpSample t=" 152 " lt=" 128 " ts=" 1359631725190 " s=" true " lb=" baidu " rc=" 200 " rm=" OK " tn=" sets of threads 1-1 " dt=" text " by=" 10063 "/>
Wherein, t is the response time; Lt is time delay; Ts is the request initiation time; Whether s is successful for asking; Lb is request title, etc.
Sub-step S113, stores described performance and continues the lasting integration testing destination file of integration testing record generation performance.
As a kind of preferred exemplary of the present embodiment, it can be the suffix xml formatted file that is .jtl that described performance continues integration testing destination file, and this file has that file is large, performance continues the characteristics such as integration testing records more than number.
Step 102, continues integration testing record by described many performances and reads to one by one in internal memory;
In specific implementation, described performance continues integration testing destination file and is stored in disk, for read-only file, Performance plugin is in the time that the lasting integration testing of analysis feature records, lasting described performance integration testing record need to be written in internal memory and resolve, in the prior art, the lasting integration testing record of over-all properties that Performance plugin continues described performance in integration testing destination file is written in internal memory, if the parsing of a lasting integration testing destination file of performance need to be written into 300M data, get so 10 structure information and just need the memory headroom of nearly 3G, not only can cause JVM(Java virtual machine) constantly carry out frequently garbage reclamation, the risk that even there will be internal memory to overflow.In actual scene, once find, resolve a performance that builds number of times 15 and continue integration servers, or resolve while exceeding the lasting integration servers of 5 performances, will directly cause Hudson that service cannot be provided.
In order to prevent that huge performance is continued to integration testing destination file is written into internal memory, and cause low memory, the embodiment of the present application adopts a buffer queue, described performance is continued to integration testing record and be written in the buffer queue of internal memory by the lasting integration testing request of each performance.
Step 103, continues integration testing record to the performance in described internal memory and resolves, and obtains corresponding intermediate performance achievement data;
In a preferred embodiment of the present application, described step 103 can comprise following sub-step:
Sub-step S21, continues integration testing record by described many performances and reads to one by one in the buffer queue arranging in internal memory;
Sub-step S22 reads one by one described performance and continues integration testing record from described buffer queue, calculates intermediate performance achievement data according to default statistical rules;
In practice, a lot of attributes that performance continues in integration testing record are not necessary, conventional just some crucial attributes, therefore be applied to the embodiment of the present application, adopt a computational threads from described buffer queue, to take out specially performance and continue integration testing record, extract conventional crucial attribute, and calculate according to default statistical rules, obtain intermediate performance achievement data.
As a kind of preferred exemplary of the present embodiment, described intermediate performance achievement data can comprise average response time (avt), request sum (sum), error rate (err), maximum response time (max), Best-case Response Time (min), handling capacity (tps) etc., the process of described calculating intermediate performance achievement data is as follows:
Before starting to calculate, first define several variablees: response time of all requests (resolve a performance at every turn and continue integration testing record, just the response time in record is increased in this variable), the request start time, the request end time, maximum response time, Best-case Response Time.
Computational threads is taken out a performance and is continued integration testing while recording from buffer queue so, just starts to calculate:
Average response time (avt): all response time/sum of avt=;
Request sum (sum): resolve one at every turn, just add 1;
Error rate: be wrong sum/sum;
Maximum response time: get response time and maximum response time comparison in record, if the response time in record is greater than maximum response time, the response time of record is replaced with to maximum response time, otherwise maximum response time is constant;
Best-case Response Time: get response time and Best-case Response Time comparison in record, if the response time in record is less than Best-case Response Time, the response time in record is replaced with to Best-case Response Time, otherwise Best-case Response Time is constant;
Handling capacity (tps): successfully request sum/(end time-start time).
Resolve from above-mentioned calculating, each computing all only can be processed in above-mentioned several performance index data, and 100 so, and 10000 is also like this.So just, save internal memory, also obtained the performance index data of most critical.
Step 104, the performance being parsed described in deleting in internal memory continues integration testing record;
Particularly, because if retention property continues every lasting integration testing record of performance in integration testing destination file in internal memory, will expend a large amount of internal memory (for example 300M).In the embodiment of the present application, extract and calculate after performance index data by computational threads, this that calculating is completed a performance continues integration testing record and removes from internal memory, thereby has saved memory headroom.Experimental data proves, adopts after the technical scheme of the embodiment of the present application, only needs the memory headroom of 4k left and right just can complete the parsing of the lasting integration testing record of whole performances, has saved widely memory headroom.
Step 105, judges whether the lasting integration testing record of many performances that described performance continues in integration testing destination file is parsed; If so, perform step 106, if not, return to step 102;
In a preferred embodiment of the present application, described step 105 can comprise following sub-step:
Sub-step S31, judges that described performance continues integration testing record and whether comprises default end mark; If so, carry out sub-step S32; If not, carry out sub-step S33;
Sub-step S32, the lasting integration testing record of many performances being judged as in the lasting integration testing destination file of described performance is parsed;
Sub-step S33, the lasting integration testing record of many performances being judged as in the lasting integration testing destination file of described performance is not parsed.
In specific implementation, in the time that lasting the last item performance of the lasting integration testing destination file of performance integration testing record is written into the buffer queue of internal memory, can continue integration testing record to this performance and add that is finished a mark, represent that this performance continues integration testing destination file and read complete.Therefore, in the time that the lasting integration testing record of described performance comprises default end mark, represent that described performance continues integration testing and is recorded as the last item record in the lasting integration testing destination file of performance, the lasting integration testing record of many performances that described performance continues in integration testing destination file is parsed.
Step 106, obtains final performance achievement data, and the performance of deleting in disk continues integration testing destination file;
Wherein, described final performance achievement data is the intermediate performance achievement data that the performance that comprises default end mark continues integrated record correspondence, particularly, not that performance is when continuing the last item in integration testing destination file and recording when described performance continues integration testing record, calculating the performance index data that obtain is intermediate performance achievement data, in the time that described performance continues integration testing and is recorded as performance and continues the last item in integration testing destination file and record, calculating the performance index data that obtain is final performance achievement data.
Continue in Integrated scenario in actual performance, one time performance continued the integrated operation time at 10～15 minutes, the performance generating continues that integration testing destination file is minimum comprises that ten thousand performances of 9-20 continue integration testing record, and in the time that tps reaches 5000, can produce 2,400,000 performances and continue integration testing record, the mean size of every lasting integration testing record of performance is 200b, once will produce the data of nearly 300M.Be to carry out once minimum every day if performance continues Integrated scenario, most historic task builds and has exceeded 100 times, just 1 lasting integration servers of performance at least needs 29G disk space so.Constantly increase if performance continues integration servers, will need a large amount of disk spaces.In the embodiment of the present application, obtaining after final performance achievement data, from disk, deleting original performance and continue integration testing destination file, to reach the object of saving disk space.
Step 107, is stored to described final performance achievement data in internal memory and disk.
Particularly, obtaining after final performance achievement data, it is being preserved in internal memory to portion, can quick obtaining performance index data while inquiry for external interface.
Simultaneously to continue integration testing destination file in order ensureing after application is restarted without analysis feature again, described final performance achievement data can be write in disk file.In actual applications, in the time that the lasting integration testing destination file size of performance is 300M, scheme of the prior art will expend respectively the space size of internal memory and the nearly 300M of disk, and in the embodiment of the present application, final performance achievement data 2k left and right only in internal memory and disk, only about 1k of disk file, has saved the space of internal memory and disk greatly, and delay because plug-in unit the is unstable probability of machine of Hudson also greatly reduces.
The data layout that described final performance achievement data is kept in disk and internal memory can be expressed as follows:
<performanceReportMap>
<reportBuild>
<average>58</average>
<avrgDiff>0</avrgDiff>
<errCounts>0</errCounts>
<errPercDiff>0.0</errPercDiff>
<errPercent>0.0</errPercent>
<line90>79</line90>
<max>768</max>
<median>60</median>
<medianDiff>0</medianDiff>
<min>4</min>
<size>400467</size>
<sizeDiff>0</sizeDiff>
<tps>669.68</tps>
<tpsDiff>0.0</tpsDiff>
<uriReport>...</uriReport>
</reportBuild>
</performanceReportMap>
In a preferred embodiment of the present application, described step 107 can comprise following sub-step:
Sub-step S51, obtains the performance corresponding with described final performance achievement data and continues integration servers title and/or the lasting integration servers numbering of performance;
Sub-step S52, the mapping relations that described final performance achievement data, final performance achievement data and described performance continued to integration servers title and/or the lasting integration servers numbering of performance are stored in internal memory and disk.
Particularly, in internal memory and disk, storage object is to continue integration servers title and/or performance according to performance to continue integration servers and number to safeguard itself and the corresponding relation of final performance achievement data.
With reference to Fig. 3, show the flow chart of steps that a kind of performance continues the embodiment of the method 1 that reads of integrated data, the method that the lasting integrated data of described performance reads is specifically as follows the method that reads described final performance achievement data from internal memory or disk, specifically can comprise the steps:
Step 201, receptivity achievement data inquiry request, the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
Step 202 is searched described performance and is continued integration servers title and/or the lasting integration servers numbering of performance in internal memory;
Step 203, if search successfully, obtains with the lasting integration servers title of described performance and/or performance and continues final performance achievement data corresponding to integration servers numbering and return;
Step 204, if search unsuccessfully, continues integration servers title and/or the lasting integration servers numbering of performance spanned file path according to described performance; In disk, read described final performance achievement data according to described file path.
In specific implementation, because performance continues being built with repeatedly of integration servers, for example need to check structure 1～200 time, just can directly be written into the performance index data of having resolved from internal memory or disk, do not need again to resolve, the granularity of the performance index data of buffer memory is thinner like this.
In internal memory and disk, storage object is the corresponding relation that continues integration servers title and/or performance and continue integration servers and number to safeguard itself and performance index data according to performance, therefore in the time receiving the lasting integration servers title of described performance and/or the lasting integration servers numbering of performance, first in internal memory, search with the lasting integration servers title of described performance and/or the lasting integration servers of performance and number corresponding performance index data, if searched in internal memory unsuccessfully, according to preset rules, continue integration servers title and the lasting integration servers numbering of performance spanned file pathname by described performance, be placed in internal memory to reading performance achievement data in disk, next time, access just can directly be read from internal memory.Application the embodiment of the present application makes the very quick of query performance achievement data change, and in concrete application, the scheme of employing prior art is carried out query performance achievement data needs 20-40s, and the scheme of the embodiment of the present application needs 1s left and right to complete.
With reference to Fig. 4, show the flow chart of steps that a kind of performance continues the embodiment of the method 2 that reads of integrated data, the method that the lasting integrated data of described performance reads is specifically as follows the method that reads described final performance achievement data from internal memory or disk, specifically can comprise the steps:
Step 301: receive the performance index data query request that external system sends, the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
Step 302: continue the link data of integration servers title and/or the default form of performance lasting integration servers numbering generation and return according to described performance;
Step 303: receive the links and accesses of external system, obtain final performance achievement data and return from internal memory or disk according to described links and accesses.
Be applied to the embodiment of the present application, can also open described performance index data, offer external system access in URL mode, external system docking application just can easily be obtained task and be built information like this.Particularly, the application by performance index data with api interface opening to external system, external system can be obtained by HTTP the data of XML or JSON form, thereby convenient and peripheral system is integrated.For example, have a performance to continue integration servers, name is called:
162_zhizhen.wangzz_wsproductReadserver.FindAEProductById
Obtain the result building for its 234th time if want, external system only need to be initiated following http request
Http: // 10.20.142.52:8080/hudson/job/162_zhizhen.wangzz_wsproduc tRe adserver.FindAEProductById/234/performance/api/xml(xml form)
Http: // 10.20.142.52:8080/hudson/job/162_zhizhen.wangzz_wsproduc tRe adserver.FindAEProductById/234/performance/api/json(json form)
Just can obtain the performance index data that build for the 234th time:
<performanceReportMap>
<reportBuild>
<average>58</average>
<avrgDiff>0</avrgDiff>
<errCounts>0</errCounts>
<errPercDiff>0.0</errPercDiff>
<errPercent>0.0</errPercent>
<line90>79</line90>
<max>768</max>
<median>60</median>
<medianDiff>0</medianDiff>
<min>4</min>
<size>400467</size>
<sizeDiff>0</sizeDiff>
<tps>669.68</tps>
<tpsDiff>0.0</tpsDiff>
<uriReport>...</uriReport>
</reportBuild>
</performanceReportMap>
In the embodiment of the present application, provide a general performance to continue integrated solution, can improve greatly the storage of performance index data and read, and it can have been shared by other external systems easily.It should be noted that, Performance Plugin plug-in unit in the embodiment of the present application, Jmeter instrument are only exemplary, those skilled in the art can adopt other plug-in units and other testing tools to be all fine according to actual needs, the application to this without being limited.
It should be noted that, for embodiment of the method, for simple description, therefore it is all expressed as to a series of combination of actions, but those skilled in the art should know, the application is not subject to the restriction of described sequence of movement, because according to the application, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in instructions all belongs to preferred embodiment, and related action might not be that the application is necessary.
With reference to Fig. 5, show the structured flowchart of the memory storage embodiment of the lasting integrated data of a kind of performance, specifically can comprise with lower module:
File acquisition module 401, the performance that is stored in disk for obtaining continues integration testing destination file, and described performance continues integration testing destination file and comprises that many performances continue integration testing record;
In a preferred embodiment of the present application, described file acquisition module 401 can comprise following submodule:
Tasks carrying submodule, in the time meeting the trigger condition of the lasting integration servers of performance, carries out described performance and continues integration servers;
In a preferred embodiment of the present application, described tasks carrying submodule further can comprise with lower unit:
Request initiating cell, continues integration testing request for initiating performance;
Record acquiring unit, for continue integration testing request according to described initiation performance, described performance is continued to the lasting integration testing of integration servers execution performance, obtain performance and continue integration testing record;
File generating unit, continues the lasting integration testing destination file of integration testing record generation performance for storing described performance.
Record insmods 402, reads to one by one internal memory for described many performances being continued to integration testing record;
Record parsing module 403, resolve for the performance of described internal memory being continued to integration testing record, obtain corresponding intermediate performance achievement data;
In a preferred embodiment of the present application, the described parsing module 403 that records can comprise following submodule:
Buffer queue is put into submodule, reads to one by one in the buffer queue arranging at internal memory for described many performances being continued to integration testing record;
Intermediate performance achievement data calculating sub module, continues integration testing record for read one by one described performance from described buffer queue, calculates intermediate performance achievement data according to default statistical rules;
Record removing module 404, for continuing integration testing record in the performance being parsed described in internal memory deletion;
Judge module 405, for judging that many performances of the lasting integration testing destination file of described performance continue integration testing record and whether are parsed; If so, call final performance achievement data and obtain module 406; If not, call record and insmod 402;
In a preferred embodiment of the present application, described judge module 405 can comprise following submodule:
Default end mark judges submodule, for judging that described performance continues integration testing record and whether comprises default end mark; If so, call and be parsed judgement submodule;
Be parsed judgement submodule, many performances that continue integration testing destination file for being judged as described performance continue integration testing record and are parsed.
Wherein, described final performance achievement data is that the lasting integration testing of performance that comprises default end mark records corresponding intermediate performance achievement data.
File removing module 407, continues integration testing destination file for the performance of deleting disk;
Final performance achievement data memory module 408, for being stored to internal memory and disk by described final performance achievement data.
In a preferred embodiment of the present application, described final performance achievement data memory module 408 can comprise following submodule:
Performance continues integration servers acquisition of information submodule, and for obtaining, the performance corresponding with described final performance achievement data continues integration servers title and/or performance continues integration servers numbering;
Sub module stored, is stored to internal memory and disk for the mapping relations that described final performance achievement data, final performance achievement data and described performance continued to integration servers title and/or the lasting integration servers numbering of performance.
Be applied to the embodiment of the present application, if continuing integration servers, performance has 28, each performance continues integration servers structure number of times and becomes to exceed 200 times, and performance continues the total size of integration testing destination file less than 30M, the reading speed of performance index data is lower than 1s, the Hudson machine of never delaying because plug-in unit is unstable.
Because the device embodiment of described Fig. 5 is substantially corresponding to earlier figures 2 embodiments of the method, therefore not detailed part in the description of the present embodiment can, referring to the related description in earlier figures 2 embodiment, just not repeat at this.
The application also provides a kind of performance to continue the device embodiment that integrated data reads, and specifically can comprise with lower module:
Final performance achievement data read module, for reading described final performance achievement data from internal memory or disk.
In a preferred embodiment of the present application, described final performance achievement data read module can comprise following submodule:
Request receiving submodule, for receptivity achievement data inquiry request, the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
Search submodule, for searching at internal memory, described performance continues integration servers title and/or performance continues integration servers numbering;
Return to submodule, while searching successfully for continue the lasting integration servers numbering of integration servers title and/or performance in described performance, obtain with the lasting integration servers title of described performance and/or the lasting integration servers of performance and number corresponding performance index data and return;
File path generation submodule, while searching unsuccessfully, continues integration servers according to the lasting integration servers title of described performance and/or performance and numbers spanned file path for continue the lasting integration servers numbering of integration servers title and/or performance in described performance; In disk, read described final performance achievement data according to described file path.
In another preferred embodiment of the present application, described final performance achievement data read module can comprise following submodule:
External system inquiry request receives submodule, the performance index data query request sending for receiving external system, and the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
Link data generates submodule, generates the link data of default form and returns for continue the lasting integration servers numbering of integration servers title and/or performance according to described performance;
Performance index data are returned to submodule, for receiving the links and accesses of external system, obtain final performance achievement data and return according to described links and accesses from internal memory or disk.
Because said apparatus embodiment is substantially corresponding to earlier figures 4 embodiments of the method, therefore not detailed part in the description of the present embodiment can, referring to the related description in earlier figures 3 embodiment, just not repeat at this.
Each embodiment in this instructions all adopts the mode of going forward one by one to describe, and what each embodiment stressed is and the difference of other embodiment, between each embodiment identical similar part mutually referring to.For device embodiment, because it is substantially similar to embodiment of the method, so description is fairly simple, relevant part is referring to the part explanation of embodiment of the method.
Those skilled in the art should understand, the application's embodiment can be provided as method, system or computer program.Therefore, the application can adopt complete hardware implementation example, completely implement software example or the form in conjunction with the embodiment of software and hardware aspect.And the application can adopt the form at one or more upper computer programs of implementing of computer-usable storage medium (including but not limited to magnetic disk memory, CD-ROM, optical memory etc.) that wherein include computer usable program code.
The application is with reference to describing according to process flow diagram and/or the block scheme of the method for the embodiment of the present application, equipment (system) and computer program.Should understand can be by the flow process in each flow process in computer program instructions realization flow figure and/or block scheme and/or square frame and process flow diagram and/or block scheme and/or the combination of square frame.Can provide these computer program instructions to the processor of multi-purpose computer, special purpose computer, Embedded Processor or other programmable data processing device to produce a machine, the instruction that makes to carry out by the processor of computing machine or other programmable data processing device produces the device for realizing the function of specifying at flow process of process flow diagram or multiple flow process and/or square frame of block scheme or multiple square frame.
These computer program instructions also can be stored in energy vectoring computer or the computer-readable memory of other programmable data processing device with ad hoc fashion work, the instruction that makes to be stored in this computer-readable memory produces the manufacture that comprises command device, and this command device is realized the function of specifying in flow process of process flow diagram or multiple flow process and/or square frame of block scheme or multiple square frame.
These computer program instructions also can be loaded in computing machine or other programmable data processing device, make to carry out sequence of operations step to produce computer implemented processing on computing machine or other programmable devices, thereby the instruction of carrying out is provided for realizing the step of the function of specifying in flow process of process flow diagram or multiple flow process and/or square frame of block scheme or multiple square frame on computing machine or other programmable devices.
Although described the application's preferred embodiment, once those skilled in the art obtain the basic creative concept of cicada, can make other change and amendment to these embodiment.So claims are intended to be interpreted as comprising preferred embodiment and fall into all changes and the amendment of the application's scope.
Finally, also it should be noted that, in this article, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thereby the process, method, article or the equipment that make to comprise a series of key elements not only comprise those key elements, but also comprise other key elements of clearly not listing, or be also included as the intrinsic key element of this process, method, article or equipment.The in the situation that of more restrictions not, the key element being limited by statement " comprising ... ", and be not precluded within process, method, article or the equipment that comprises described key element and also have other identical element.
The method and apparatus that a kind of performance above the application being provided continues integrated data processing is described in detail, applied principle and the embodiment of specific case to the application herein and set forth, the explanation of above embodiment is just for helping to understand the application's method and core concept thereof; , for one of ordinary skill in the art, according to the application's thought, all will change in specific embodiments and applications, in sum, this description should not be construed as the restriction to the application meanwhile.
Claims (16)
1. performance continues a method for integrated data processing, it is characterized in that, comprising:
Obtain the performance being stored in disk and continue integration testing destination file, described performance continues integration testing destination file and comprises that many performances continue integration testing record;
Described many performances are continued to integration testing record to be read in internal memory one by one;
Performance in described internal memory is continued to integration testing record and resolve, obtain corresponding intermediate performance achievement data;
The performance being parsed described in deleting in internal memory continues integration testing record;
Judge whether the lasting integration testing record of many performances that described performance continues in integration testing destination file is parsed;
If so, obtain final performance achievement data, and the performance of deleting in disk continues integration testing destination file;
Described final performance achievement data is stored in internal memory and disk.
2. method according to claim 1, is characterized in that, described in obtain the step that the performance that is stored in disk continues integration testing destination file and comprise:
In the time meeting the trigger condition of the lasting integration servers of performance, carry out described performance and continue integration servers;
The sub-step that described execution performance continues integration servers further comprises:
Initiate performance and continue integration testing request;
Continue integration testing request according to described performance described performance is continued to the lasting integration testing of integration servers execution performance, obtain performance and continue integration testing record;
Store described performance and continue the lasting integration testing destination file of integration testing record generation performance.
3. method according to claim 1, is characterized in that, describedly performance in internal memory is continued to integration testing record resolves, and the step that obtains corresponding intermediate performance achievement data comprises:
Described many performances are continued to integration testing record to be read in the buffer queue arranging in internal memory one by one;
From described buffer queue, read one by one described performance and continue integration testing record, calculate intermediate performance achievement data according to default statistical rules;
Describedly judge that performance continues many performances in integration testing destination file and continues integration testing and record the step whether being parsed and comprise:
Judge that described performance continues integration testing record and whether comprises default end mark;
If so, the lasting integration testing record of many performances being judged as in the lasting integration testing destination file of described performance is parsed.
4. method according to claim 3, is characterized in that, described final performance achievement data is that the lasting integration testing of performance that comprises default end mark records corresponding intermediate performance achievement data.
5. method according to claim 1, is characterized in that, the described step that final performance achievement data is stored in internal memory and disk comprises:
Obtain the performance corresponding with described final performance achievement data and continue integration servers title and/or the lasting integration servers numbering of performance;
The mapping relations that described final performance achievement data, final performance achievement data and described performance continued to integration servers title and/or the lasting integration servers numbering of performance are stored in internal memory and disk.
6. according to the method described in the arbitrary claim of claim 1-5, it is characterized in that, also comprise:
From internal memory or disk, read described final performance achievement data.
7. method according to claim 6, is characterized in that, the described step that reads final performance achievement data from internal memory or disk comprises:
Receptivity achievement data inquiry request, the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
In internal memory, search described performance and continue integration servers title and/or the lasting integration servers numbering of performance;
If search successfully, obtain with the lasting integration servers title of described performance and/or performance and continue final performance achievement data corresponding to integration servers numbering and return;
If search unsuccessfully, continue integration servers title and/or the lasting integration servers numbering of performance spanned file path according to described performance; In disk, read described final performance achievement data according to described file path.
8. method according to claim 6, is characterized in that, the described step that reads final performance achievement data from internal memory or disk comprises:
Receive the performance index data query request that external system sends, the request of described performance index data query comprises that performance continues integration servers title, and performance continues integration servers numbering;
Continue the link data of integration servers title and/or the default form of performance lasting integration servers numbering generation and return according to described performance;
Receive the links and accesses of external system, from internal memory or disk, obtain final performance achievement data and return according to described links and accesses.
9. performance continues a device for integrated data processing, it is characterized in that, comprising:
File acquisition module, the performance that is stored in disk for obtaining continues integration testing destination file, and described performance continues integration testing destination file and comprises that many performances continue integration testing record;
Record insmods, and reads to one by one internal memory for described many performances being continued to integration testing record;
Record parsing module, resolve for the performance of described internal memory being continued to integration testing record, obtain corresponding intermediate performance achievement data;
Record removing module, for continuing integration testing record in the performance being parsed described in internal memory deletion;
Judge module, for judging that many performances of the lasting integration testing destination file of described performance continue integration testing record and whether are parsed; If so, call final performance achievement data and obtain module;
Final performance achievement data obtains module, for obtaining final performance achievement data;
File removing module, continues integration testing destination file for the performance of deleting disk;
Final performance achievement data memory module, for being stored to internal memory and disk by described final performance achievement data.
10. device according to claim 9, is characterized in that, described file acquisition module comprises following submodule:
Tasks carrying submodule, in the time meeting the trigger condition of the lasting integration servers of performance, carries out described performance and continues integration servers;
Described tasks carrying submodule further comprises with lower unit:
Request initiating cell, continues integration testing request for initiating performance;
Record acquiring unit, for continue integration testing request according to described performance, described performance is continued to the lasting integration testing of integration servers execution performance, obtain performance and continue integration testing record;
File generating unit, continues the lasting integration testing destination file of integration testing record generation performance for storing described performance.
11. devices according to claim 9, is characterized in that, the described parsing module that records comprises following submodule:
Buffer queue is put into submodule, reads to one by one in the buffer queue arranging at internal memory for described many performances being continued to integration testing record;
Intermediate performance achievement data calculating sub module, continues integration testing record for read one by one described performance from described buffer queue, calculates intermediate performance achievement data according to default statistical rules;
Described judge module comprises following submodule:
Default end mark judges submodule, for judging that described performance continues integration testing record and whether comprises default end mark; If so, call and be parsed judgement submodule;
Be parsed judgement submodule, many performances that continue integration testing destination file for being judged as described performance continue integration testing record and are parsed.
12. devices according to claim 11, is characterized in that, described final performance achievement data is that the lasting integration testing of performance that comprises default end mark records corresponding intermediate performance achievement data.
13. devices according to claim 9, is characterized in that, described final performance achievement data memory module comprises:
Performance continues integration servers acquisition of information submodule, and for obtaining, the performance corresponding with described final performance achievement data continues integration servers title and/or performance continues integration servers numbering;
Sub module stored, is stored to internal memory and disk for the mapping relations that described final performance achievement data, final performance achievement data and described performance continued to integration servers title and/or the lasting integration servers numbering of performance.
14. according to the device described in the arbitrary claim of claim 9-13, it is characterized in that, also comprises:
Final performance achievement data read module, for reading described final performance achievement data from internal memory or disk.
15. devices according to claim 14, is characterized in that, described final performance achievement data read module comprises following submodule:
Request receiving submodule, for receptivity achievement data inquiry request, the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
Search submodule, for searching at internal memory, described performance continues integration servers title and/or performance continues integration servers numbering;
Return to submodule, while searching successfully for continue the lasting integration servers numbering of integration servers title and/or performance in described performance, obtain with the lasting integration servers title of described performance and/or performance and continue final performance achievement data corresponding to integration servers numbering and return;
File path generation submodule, while searching unsuccessfully, continues integration servers according to the lasting integration servers title of described performance and/or performance and numbers spanned file path for continue the lasting integration servers numbering of integration servers title and/or performance in described performance; In disk, read described final performance achievement data according to described file path.
16. devices according to claim 14, is characterized in that, described final performance achievement data read module comprises following submodule:
External system inquiry request receives submodule, the performance index data query request sending for receiving external system, and the request of described performance index data query comprises that performance continues integration servers title, performance continues integration servers numbering;
Link data generates submodule, generates the link data of default form and returns for continue the lasting integration servers numbering of integration servers title and/or performance according to described performance;
Performance index data are returned to submodule, for receiving the links and accesses of external system, obtain final performance achievement data and return according to described links and accesses from internal memory or disk.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310072553.3A CN104035938A (en) | 2013-03-07 | 2013-03-07 | Performance continuous integration data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310072553.3A CN104035938A (en) | 2013-03-07 | 2013-03-07 | Performance continuous integration data processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104035938A true CN104035938A (en) | 2014-09-10 |
Family
ID=51466709
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310072553.3A Pending CN104035938A (en) | 2013-03-07 | 2013-03-07 | Performance continuous integration data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104035938A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104375937A (en) * | 2014-11-19 | 2015-02-25 | 福建亿榕信息技术有限公司 | Continuous integration method and system of automated testing results |
| CN106326092A (en) * | 2015-06-25 | 2017-01-11 | 阿里巴巴集团控股有限公司 | Integration test method and device |
| CN106598824A (en) * | 2016-11-25 | 2017-04-26 | 深圳前海微众银行股份有限公司 | Performance analysis method and device for block chain |
| CN107391327A (en) * | 2017-06-30 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of performance test methods of storage device, device and server |
| CN108984575A (en) * | 2017-06-05 | 2018-12-11 | 上海华岭集成电路技术股份有限公司 | A kind of three dimension system IC wafers test probe station data structure store method |
| CN110069402A (en) * | 2019-03-21 | 2019-07-30 | 中国平安财产保险股份有限公司 | Method, apparatus, computer equipment and the storage medium of test software |
| CN111538926A (en) * | 2020-04-20 | 2020-08-14 | 北京达佳互联信息技术有限公司 | Automatic offline package publishing method and device, electronic equipment and storage medium |
| CN112286795A (en) * | 2020-09-28 | 2021-01-29 | 长沙市到家悠享网络科技有限公司 | Software testing method, device and storage medium |
| CN112286796A (en) * | 2020-09-29 | 2021-01-29 | 长沙市到家悠享网络科技有限公司 | Software testing method, device and storage medium |
| CN113296945A (en) * | 2021-05-20 | 2021-08-24 | 山东云海国创云计算装备产业创新中心有限公司 | Continuous integration method, system, equipment and computer readable storage medium |
| CN117370216A (en) * | 2023-12-08 | 2024-01-09 | 天津华来科技股份有限公司 | Callback interface performance test method based on python language |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020178260A1 (en) * | 2001-05-23 | 2002-11-28 | Chang Hsin-Wang Wayne | Distributed computer resource bartering system |
| CN101364217A (en) * | 2007-08-08 | 2009-02-11 | 华为技术有限公司 | Data maintenance method, equipment and system thereof in data-base |
| CN101571872A (en) * | 2009-06-11 | 2009-11-04 | 北京百分通联传媒技术有限公司 | Network data processing method and system |
| CN102799670A (en) * | 2012-07-16 | 2012-11-28 | 北京国创富盛通信股份有限公司 | Pressure test data processing device and pressure test data processing method |
-
2013
- 2013-03-07 CN CN201310072553.3A patent/CN104035938A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020178260A1 (en) * | 2001-05-23 | 2002-11-28 | Chang Hsin-Wang Wayne | Distributed computer resource bartering system |
| CN101364217A (en) * | 2007-08-08 | 2009-02-11 | 华为技术有限公司 | Data maintenance method, equipment and system thereof in data-base |
| CN101571872A (en) * | 2009-06-11 | 2009-11-04 | 北京百分通联传媒技术有限公司 | Network data processing method and system |
| CN102799670A (en) * | 2012-07-16 | 2012-11-28 | 北京国创富盛通信股份有限公司 | Pressure test data processing device and pressure test data processing method |
Non-Patent Citations (1)
| Title |
|---|
| 江新: ""基于JMeter的MS Web应用系统的性能测试研究"", 《万方数据企业知识服务平台》 * |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104375937A (en) * | 2014-11-19 | 2015-02-25 | 福建亿榕信息技术有限公司 | Continuous integration method and system of automated testing results |
| CN106326092A (en) * | 2015-06-25 | 2017-01-11 | 阿里巴巴集团控股有限公司 | Integration test method and device |
| CN106326092B (en) * | 2015-06-25 | 2019-02-19 | 阿里巴巴集团控股有限公司 | A kind of integration test method and device |
| CN106598824A (en) * | 2016-11-25 | 2017-04-26 | 深圳前海微众银行股份有限公司 | Performance analysis method and device for block chain |
| CN108984575B (en) * | 2017-06-05 | 2021-08-06 | 上海华岭集成电路技术股份有限公司 | Three-dimensional system integrated circuit wafer test probe station data structure storage method |
| CN108984575A (en) * | 2017-06-05 | 2018-12-11 | 上海华岭集成电路技术股份有限公司 | A kind of three dimension system IC wafers test probe station data structure store method |
| CN107391327A (en) * | 2017-06-30 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of performance test methods of storage device, device and server |
| CN110069402A (en) * | 2019-03-21 | 2019-07-30 | 中国平安财产保险股份有限公司 | Method, apparatus, computer equipment and the storage medium of test software |
| CN111538926A (en) * | 2020-04-20 | 2020-08-14 | 北京达佳互联信息技术有限公司 | Automatic offline package publishing method and device, electronic equipment and storage medium |
| CN112286795A (en) * | 2020-09-28 | 2021-01-29 | 长沙市到家悠享网络科技有限公司 | Software testing method, device and storage medium |
| CN112286796A (en) * | 2020-09-29 | 2021-01-29 | 长沙市到家悠享网络科技有限公司 | Software testing method, device and storage medium |
| CN113296945A (en) * | 2021-05-20 | 2021-08-24 | 山东云海国创云计算装备产业创新中心有限公司 | Continuous integration method, system, equipment and computer readable storage medium |
| CN117370216A (en) * | 2023-12-08 | 2024-01-09 | 天津华来科技股份有限公司 | Callback interface performance test method based on python language |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104035938A (en) | Performance continuous integration data processing method and device | |
| CN107463632B (en) | Distributed NewSQL database system and data query method | |
| US10534773B2 (en) | Intelligent query parameterization of database workloads | |
| WO2017020637A1 (en) | Task allocation method and task allocation apparatus for distributed data calculation | |
| US9491238B2 (en) | Rapid client-side component processing based on component relationships | |
| US8949558B2 (en) | Cost-aware replication of intermediate data in dataflows | |
| US9514184B2 (en) | Systems and methods for a high speed query infrastructure | |
| JPWO2011071010A1 (en) | Load characteristic estimation system, load characteristic estimation method and program | |
| CA3167981C (en) | Offloading statistics collection | |
| CN110807145A (en) | Query engine acquisition method, device and computer-readable storage medium | |
| WO2019005403A1 (en) | Query optimization using propagated data distinctness | |
| CN111488323B (en) | Data processing method and device and electronic equipment | |
| CN111488736A (en) | Self-learning word segmentation method and device, computer equipment and storage medium | |
| CN110222046B (en) | List data processing method, device, server and storage medium | |
| CN110851452B (en) | Data table connection processing method and device, electronic equipment and storage medium | |
| CN109213972B (en) | Method, device, equipment and computer storage medium for determining document similarity | |
| US20210360005A1 (en) | Inferring watchpoints for understandable taint reports | |
| CN112765200A (en) | Data query method and device based on Elasticissearch | |
| EP2990960A1 (en) | Data retrieval via a telecommunication network | |
| CN113268487B (en) | Data statistical method, device and computer readable storage medium | |
| CN113297245A (en) | Method and device for acquiring execution information | |
| US20190026748A1 (en) | Mobile wireless customer micro-care apparatus and method | |
| US20120284315A1 (en) | Optimization of non-deterministic computational paths | |
| Dai et al. | The Hadoop stack: new paradigm for big data storage and processing | |
| CN116910082A (en) | SQL sentence processing method, device, server and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20140910 |
|
| WD01 | Invention patent application deemed withdrawn after publication |