CN107767264A - Online transaction system focus account trading flow pressure real-time monitoring method and device - Google Patents
Online transaction system focus account trading flow pressure real-time monitoring method and device Download PDFInfo
- Publication number
- CN107767264A CN107767264A CN201711020188.6A CN201711020188A CN107767264A CN 107767264 A CN107767264 A CN 107767264A CN 201711020188 A CN201711020188 A CN 201711020188A CN 107767264 A CN107767264 A CN 107767264A
- Authority
- CN
- China
- Prior art keywords
- account
- transaction
- accumulation table
- accumulation
- current
- 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
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000012544 monitoring process Methods 0.000 title abstract description 6
- 238000009825 accumulation Methods 0.000 claims abstract description 91
- 238000012545 processing Methods 0.000 claims description 24
- 230000001186 cumulative effect Effects 0.000 claims description 9
- 238000010926 purge Methods 0.000 claims 1
- 230000008569 process Effects 0.000 abstract description 7
- 230000006872 improvement Effects 0.000 description 8
- 238000012423 maintenance Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000001276 controlling effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 238000003860 storage Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000000052 comparative effect Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000011946 reduction process Methods 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 238000003892 spreading Methods 0.000 description 1
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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application embodiment discloses a kind of online transaction system focus account trading flow pressure real-time monitoring method and device, wherein, method includes：Initial time is performed in any account trading, account trading accumulation schedule is accessed, judges that this trading account currently accumulates whether transaction count exceedes preset value；Wherein, if it exceeds preset value, then the account is current focus account；If the account that this described transaction includes is focus account, and last transaction accesses database and performance issue occurs, merchandises and enters line delay wait according to the duration of setting, and delay enters this account trading handling process after waiting；After transaction process flow is finished, the relevant information on the account in the account trading accumulation schedule is updated, realizes the regulation and control of focus account trading flow pressure.
Description
Technical Field
The application relates to the technical field of data processing, in particular to a real-time regulation and control method and device for transaction flow pressure of a hotspot account of an online transaction system.
Background
An online transaction system: an online processing system featuring transaction processing, where a transaction comprises one or more transactions with concurrent processing capabilities on access to resources such as databases, files, networks, etc. Under the pressure of large concurrency, the online transaction system is easy to generate hot account and cause database performance problem. In the online transaction system application maintenance process, the hotspot account is discovered by the analysis system or the application log after the transaction performance is reduced or the failure rate is increased. Meanwhile, the regulation and control of the hot account are only limited to the requirement that the transaction requesting party reduces the transaction submitting frequency afterwards, and the regulation and control cannot be carried out in real time. Therefore, during system maintenance, only hot accounts can be found by analyzing the system or application logs. On one hand, if the account information is lacked in the log, the hotspot account cannot be known; on the other hand, opening the log also has an impact on the online performance.
In summary, the prior art lacks an automatic regulation and control means for hotspot account transaction, and is limited to require a transaction requesting party to reduce transaction submission frequency after the transaction, and loses the regulation and control significance because the time interval from the hotspot occurrence is long.
Disclosure of Invention
The technical scheme solves the problems that a transaction system monitors a hotspot account in real time and automatically adjusts the transaction peak pressure. The method has important practical significance for maintenance work such as real-time performance monitoring of an application system under large concurrent pressure, automatic peak clipping of transaction pressure and the like.
In order to achieve the above object, an embodiment of the present application provides a method for real-time regulating and controlling transaction traffic pressure of a hotspot account in an online transaction system, including:
at the initial moment of executing any account transaction, accessing an account transaction accumulation table, and judging whether the current accumulated transaction times of the current transaction account exceeds a preset value; if the current hotspot account exceeds the preset value, the account is the current hotspot account;
if the account included in the transaction is a hot account and the performance problem occurs when the database is accessed in the previous transaction, the transaction is subjected to delay waiting according to the set duration, and the transaction processing flow of the account is entered after the delay waiting;
and after the transaction processing flow is executed, updating the related information about the account in the account transaction accumulation table to realize the regulation and control of the transaction flow pressure of the hotspot account.
Preferably, the method further comprises the following steps:
setting an account transaction accumulation table, and recording the key field of each account in the latest time period in the account transaction accumulation table; wherein the key fields of the account transaction accumulation table include: start time, account number, cumulative number of transactions, whether a performance issue occurred, transaction timestamp, and record status.
Preferably, the method further comprises the following steps:
the same account is hashed in different records in the account transaction accumulation table by a random factor.
Preferably, the account transaction accumulation table is a memory table.
Preferably, the method further comprises the following steps:
setting two account transaction accumulation tables and the switching period duration of the account transaction accumulation tables, and switching the two account transaction accumulation tables for use in turn.
Preferably, the handover method is a hard handover mode.
Preferably, the method for updating the related information about the account in the account transaction accumulation table comprises the following steps:
inquiring whether the account record exists in the account transaction accumulation table or not according to the account information, if not, adding a record, setting the transaction accumulation frequency to be 1, and setting the field of 'whether a performance problem occurs' to be 'no'; if the record exists, judging whether the interval between the starting time of the record and the current time is within a preset value, if so, changing the transaction accumulated times in the corresponding record, and adding 1 on the basis of the original transaction accumulated times; if the time difference exceeds the preset time difference range, modifying the record, taking the current moment as the initial moment corresponding to the first transaction of the account, and modifying the accumulated transaction times to be 1;
if database access performance errors occur during the account transaction processing flow, setting the field of 'whether performance problems occur' as 'yes', and otherwise, setting the field of 'no'.
Preferably, the method further comprises the following steps:
and carrying out data backup and data clearing operations on the idle account transaction accumulation table.
In order to achieve the above object, an embodiment of the present application further provides a device for real-time regulating and controlling transaction flow pressure of a hotspot account in an online transaction system, including:
the access unit is used for accessing the account transaction accumulation table at the initial execution time of any account transaction and judging whether the current accumulated transaction times of the current transaction account exceed a preset value or not; if the current hotspot account exceeds the preset value, the account is the current hotspot account;
the delay unit is used for carrying out delay waiting on the transaction according to the set duration when the account included in the transaction is a hotspot account and the performance problem occurs when the last transaction accesses the database, and entering the transaction processing flow of the account after the delay waiting;
and the updating unit is used for updating the related information about the account in the account transaction accumulation table after the transaction processing flow is executed, so as to realize the regulation and control of the transaction flow pressure of the hotspot account.
Preferably, the system further comprises an account transaction accumulation table setting unit, wherein,
the account transaction accumulation table setting unit is used for setting an account transaction accumulation table and recording the key field of each account in the latest time period in the account transaction accumulation table; wherein the key fields of the account transaction accumulation table include: start time, account number, cumulative number of transactions, whether a performance issue occurred, transaction timestamp, and record status.
Preferably, the account transaction accumulation table setting unit is further configured to hash the same account in different records in the account transaction accumulation table by a random factor.
Preferably, a switching unit is further included; wherein,
the switching unit is used for setting the two account transaction accumulation tables and the switching cycle duration of the account transaction accumulation tables, and the two account transaction accumulation tables are switched and used in turn.
Preferably, a cleaning unit is further included; wherein,
and the clearing unit is used for carrying out data backup and data clearing operation on the idle account transaction accumulation table.
The technical scheme has the following beneficial effects:
the technical scheme can capture the hot account of the online transaction system in real time, and can solve the problems that the transaction system quickly monitors the hot account and automatically adjusts the transaction flow pressure in real time. The method has important practical significance for maintenance work such as automatic performance monitoring and automatic peak pressure adjustment of an application system.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of a method for real-time regulation and control of transaction flow pressure of a hotspot account of an online transaction system according to an embodiment of the present invention;
fig. 2 is a functional block diagram of a device for real-time regulation and control of transaction flow rate pressure of a hotspot account of an online transaction system according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art without any inventive work based on the embodiments in the present application shall fall within the scope of protection of the present application.
In the concurrent transaction processing process, a plurality of transactions need to access the same account, so as to form contention for database access, and the account is called a hotspot account. In the case of sufficient pressure, hot-spot accounts can reduce database access efficiency, resulting in transaction delays. If 2 or more transactions access multiple records of the database by locking and the access sequence is reversed, a timeout or deadlock may occur further reducing system performance.
Based on the above analysis, the working principle of the technical scheme is as follows: the technical scheme is that an account transaction accumulation table is set, and the transaction accumulation number of an account with higher popularity in a recent period of time, whether a database performance problem occurs or not and a transaction timestamp are recorded in the table; in order to avoid the table changing into a new hot table, the same account is hashed into different records according to random factors, and the total number of the records is controlled by alternately switching the two tables, so that the performance is ensured; when the transaction program starts to execute, whether the accumulated transaction number of the current account exceeds a preset value and whether a database performance problem occurs is judged, and if the accumulated transaction number exceeds the preset value, delay waiting is carried out. Therefore, the online transaction pressure is automatically controlled, and the performance problem of the transaction peak is prevented from occurring and spreading.
Based on the working principle of the present disclosure, an embodiment of the present invention provides a method for monitoring hot-spot accounts in an online transaction system in real time, as shown in fig. 1. The method comprises the following steps:
step 101): at the initial moment of executing any account transaction, accessing an account transaction accumulation table, and judging whether the current accumulated transaction times of the current transaction account exceeds a preset value; and if the account exceeds the preset value, the account is the current hotspot account.
In this embodiment, an account transaction accumulation table is set, and the transaction accumulation times, whether performance problems occur or not and the time stamp of each account in the latest time period are recorded in the account transaction accumulation table; wherein the key fields of the account transaction accumulation table include: start time, account number, cumulative number of transactions, transactions with performance issues, transaction timestamp, and record status. In the technical scheme, the transaction timestamp is a timestamp when the transaction is written in or the operation of updating the account accumulation table is executed. Table 1 below is an example of an account transaction accumulation table.
TABLE 1
In table 1, the start time indicates the time to record the first transaction, such as the time to first transaction of account 66666666 is 15:40: 36:123, there are a total of 10 transactions until the current time. The number in the transaction count field may be incremented by 1 for each transaction completed by account 66666666.
If the difference between the current time of the transaction and the start time exceeds a preset parameter (e.g., 5 seconds), the record is rewritten. For example, when 15:40:50:135 account 66666666 is about to make a transaction, the starting time of the 1 st record is rewritten to 15:40:50:135 and the number of transactions is changed to 1.
In this embodiment, for a scenario or system where hot account transactions are particularly intensive, that is, a large number of transactions of the same account number will access the account transaction accumulation table instantaneously, and recording contention may be formed due to locking when the table is written. To avoid creating a new performance bottleneck in such extreme cases, the accounts are hashed into substantially uniform records by random factors (e.g., parity may be hashed to 2 for the last digit of the transaction time millisecond value and to 10 for the value), as shown in table 2 below (an example of hashing 2 accounts by parity):
TABLE 2
By such hashing, centralized write operations to the same account record are dispersed.
When the total transaction times need to be read, the transaction times are obtained in an adding mode by 'dirty reading' of all records of the account; and when the performance problem of the database is read, the last record of the time stamp is adopted.
Step 102): if the account contained in the transaction is a hot account and the database performance problem occurs in the last transaction, the transaction is subjected to delay waiting according to the set time length, and the transaction processing flow of the account is entered after the delay waiting;
in this embodiment, when the current accumulated transaction frequency of the account included in the current transaction does not exceed the preset value or when the previous transaction has no performance problem, the normal transaction processing flow of the account can be directly entered without waiting for a delay. If the account included in the transaction is a hot account and the database performance problem occurs in the previous transaction, the transaction is subjected to delay waiting according to the set time length, and the transaction processing flow of the account is entered after the delay waiting. The transaction frequency of the hot account in the transaction is reduced by delaying waiting, and the system performance is improved.
Step 103): and after the transaction processing flow is executed, updating the related information about the account in the account transaction accumulation table to realize the regulation and control of the transaction flow pressure of the hotspot account.
In this embodiment, whether the account record exists in the account transaction accumulation table is queried, and if the account record does not exist, a record is newly added, where a "transaction accumulation number" field is 1, and a "performance problem occurrence" field is "no".
If the record exists, judging whether the interval between the starting time of the record and the current time is within a preset value, if so, changing the transaction accumulated times in the corresponding record, and adding 1 on the basis of the original transaction accumulated times; and if the time difference exceeds the preset time difference range, modifying the record, taking the current moment as the starting moment corresponding to the first transaction of the account, and modifying the accumulated times of the transactions to be 1.
If database access performance related errors occur when the account transaction processing flow is executed, for example: lock wait, timeout, or other predefined error, set "if performance problem occurred" to "yes"; otherwise, no is set.
In the embodiment, the access performance of the account transaction accumulation table is ensured, and two tables and alternate switching periods are set. In the case of large transaction amount, useless (i.e. exceeding the time period) records are increased greatly, and the useless data needs to be cleared regularly (for example, every 10 minutes) so as to reduce the system maintenance cost and the access operation cost of the account transaction accumulation table and improve the performance. For this reason, two account transaction accumulation tables are set to be used in turn, and the idle account transaction accumulation table can be used for data backup and clearing operation. And a hard switching mode is adopted when the two account transaction accumulation tables are switched, and data migration is not considered, so that the reduction process can be greatly simplified, and the data loss can be completely ignored. In addition, the account transaction accumulation table is set as a memory table, and disk IO is avoided.
In this embodiment, if the current accumulated transaction amount of the account in the account transaction accumulation table exceeds a preset threshold (for example, 20) and the database performance problem occurs in the last transaction, the delay interval of the current transaction of the account is increased, and the transaction frequency is reduced; and after the performance problem of the database does not occur in the last transaction or the accumulated transaction times are lower than a preset threshold value, canceling the transaction time interval, thereby realizing the automatic regulation and control of the transaction frequency.
As shown in fig. 2, a functional block diagram of a device for real-time monitoring of a hot spot account in an online transaction system is also provided for the embodiment of the present application. The method comprises the following steps:
the access unit 201 is configured to access an account transaction accumulation table at an initial time of executing any account transaction, and determine whether the current accumulated transaction frequency of the current transaction account exceeds a preset value; if the current hotspot account exceeds the preset value, the account is the current hotspot account;
the delay unit 202 is configured to, when an account included in the current transaction is a hotspot account, and a performance problem occurs when the previous transaction accesses the database, perform delay waiting on the transaction according to a set duration, and enter a transaction processing flow of the current account after the delay waiting;
and the updating unit 203 is used for updating the related information about the account in the account transaction accumulation table after the transaction processing flow is executed, so as to realize the regulation and control of the transaction flow pressure of the hotspot account.
In this embodiment, an account transaction accumulation table setting unit is further included, wherein,
the account transaction accumulation table setting unit is used for setting an account transaction accumulation table and recording the key field of each account in the latest time period in the account transaction accumulation table; wherein the key fields of the account transaction accumulation table include: start time, account number, cumulative number of transactions, whether a performance issue occurred, transaction timestamp, and record status.
In this embodiment, the account transaction accumulation table setting unit is further configured to hash the same account in different records in the account transaction accumulation table according to a random factor.
In this embodiment, the system further comprises a switching unit; wherein,
the switching unit is used for setting the two account transaction accumulation tables and the switching cycle duration of the account transaction accumulation tables, and the two account transaction accumulation tables are switched and used in turn.
In this embodiment, the apparatus further comprises a clearing unit; wherein,
and the clearing unit is used for carrying out data backup and data clearing operation on the idle account transaction accumulation table.
In the technical scheme, an account transaction accumulation table is required to be set and used for recording the accumulated times of account transactions in the latest time period and whether the database performance problem occurs in the last transaction in the table; the account transaction cumulative table is periodically cleaned up and the same account is hashed in different records in the account transaction cumulative table by a random factor, preventing the account transaction cumulative table from becoming a new hot table. In addition, the account transaction accumulation table is a memory table, and disk IO operation is avoided. When necessary, the transaction delay time is set, and when the transaction pressure is too high and the performance problem occurs, the hot account transaction can delay the processing flow so as to reduce the pressure. When the system performance is improved, the time delay can be cancelled, and the automatic regulation and control of the transaction pressure are realized.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most popular applications. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
Those skilled in the art will also appreciate that, in addition to implementing a client, server as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the client, server are in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a client, server may be considered as a hardware component, and the means included therein for implementing various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present application.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiments of the client, reference may be made to the introduction of the embodiments of the method described above for a comparative explanation.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
Although the present application has been described in terms of embodiments, those of ordinary skill in the art will recognize that there are numerous variations and permutations of the present application without departing from the spirit of the application, and it is intended that the appended claims encompass such variations and permutations without departing from the spirit of the application.
Claims (13)
1. A real-time regulation and control method for transaction flow pressure of a hotspot account in an online transaction system is characterized by comprising the following steps:
at the initial moment of executing any account transaction, accessing an account transaction accumulation table, and judging whether the current accumulated transaction times of the current transaction account exceeds a preset value; if the current hotspot account exceeds the preset value, the account is the current hotspot account;
if the account included in the transaction is a hot account and the performance problem occurs when the database is accessed in the previous transaction, the transaction is subjected to delay waiting according to the set duration, and the transaction processing flow of the account is entered after the delay waiting;
and after the transaction processing flow is executed, updating the related information about the account in the account transaction accumulation table to realize the regulation and control of the transaction flow pressure of the hotspot account.
2. The method of claim 1, further comprising:
setting an account transaction accumulation table, and recording the key field of each account in the latest time period in the account transaction accumulation table; wherein the key fields of the account transaction accumulation table include: start time, account number, cumulative number of transactions, whether a performance issue occurred, transaction timestamp, and record status.
3. The method of claim 2, further comprising:
the same account is hashed in different records in the account transaction accumulation table by a random factor.
4. The method of claim 1, wherein the account transaction accumulation table is a memory table.
5. The method of claim 1, further comprising:
setting two account transaction accumulation tables and the switching period duration of the account transaction accumulation tables, and switching the two account transaction accumulation tables for use in turn.
6. The method of claim 5, wherein the method of handover is a hard handover mode.
7. The method of claim 2, wherein the method of updating the information about the account in the account transaction accumulation table is by:
inquiring whether the account record exists in the account transaction accumulation table or not according to the account information, if not, adding a record, setting the transaction accumulation frequency to be 1, and setting the field of 'whether a performance problem occurs' to be 'no'; if the record exists, judging whether the interval between the starting time of the record and the current time is within a preset value, if so, changing the transaction accumulated times in the corresponding record, and adding 1 on the basis of the original transaction accumulated times; if the time difference exceeds the preset time difference range, modifying the record, taking the current moment as the initial moment corresponding to the first transaction of the account, and modifying the accumulated transaction times to be 1;
if database access performance errors occur during the account transaction processing flow, setting the field of 'whether performance problems occur' as 'yes', and otherwise, setting the field of 'no'.
8. The method of claim 5, further comprising:
and carrying out data backup and data clearing operations on the idle account transaction accumulation table.
9. The utility model provides an online transaction system hot spot account transaction flow pressure real-time regulation and control device which characterized in that includes:
the access unit is used for accessing the account transaction accumulation table at the initial execution time of any account transaction and judging whether the current accumulated transaction times of the current transaction account exceed a preset value or not; if the current hotspot account exceeds the preset value, the account is the current hotspot account;
the delay unit is used for carrying out delay waiting on the transaction according to the set duration when the account included in the transaction is a hotspot account and the performance problem occurs when the last transaction accesses the database, and entering the transaction processing flow of the account after the delay waiting;
and the updating unit is used for updating the related information about the account in the account transaction accumulation table after the transaction processing flow is executed, so as to realize the regulation and control of the transaction flow pressure of the hotspot account.
10. The apparatus of claim 9, further comprising an account transaction accumulation table setting unit, wherein,
the account transaction accumulation table setting unit is used for setting an account transaction accumulation table and recording the key field of each account in the latest time period in the account transaction accumulation table; wherein the key fields of the account transaction accumulation table include: start time, account number, cumulative number of transactions, whether a performance issue occurred, transaction timestamp, and record status.
11. The apparatus of claim 10, wherein the account transaction accumulation table setting unit is further configured to hash the same account in different records in the account transaction accumulation table by a random factor.
12. The apparatus of claim 9, further comprising a switching unit; wherein,
the switching unit is used for setting the two account transaction accumulation tables and the switching cycle duration of the account transaction accumulation tables, and the two account transaction accumulation tables are switched and used in turn.
13. The apparatus of claim 12, further comprising a purge unit; wherein,
and the clearing unit is used for carrying out data backup and data clearing operation on the idle account transaction accumulation table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711020188.6A CN107767264A (en) | 2017-10-27 | 2017-10-27 | Online transaction system focus account trading flow pressure real-time monitoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711020188.6A CN107767264A (en) | 2017-10-27 | 2017-10-27 | Online transaction system focus account trading flow pressure real-time monitoring method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107767264A true CN107767264A (en) | 2018-03-06 |
Family
ID=61271389
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711020188.6A Pending CN107767264A (en) | 2017-10-27 | 2017-10-27 | Online transaction system focus account trading flow pressure real-time monitoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107767264A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110298746A (en) * | 2019-07-04 | 2019-10-01 | 中国工商银行股份有限公司 | Hot spot account concurrent data processing system and method |
| CN110716794A (en) * | 2019-10-14 | 2020-01-21 | 网银在线（北京）科技有限公司 | Information processing method, device, system and readable storage medium |
| CN111008828A (en) * | 2019-12-28 | 2020-04-14 | 辽宁振兴银行股份有限公司 | Intelligent identification method for hot account of online transaction system |
| CN111461864A (en) * | 2020-03-31 | 2020-07-28 | 中国银行股份有限公司 | Transaction processing method and device |
| WO2021052098A1 (en) * | 2019-09-18 | 2021-03-25 | 深圳前海微众银行股份有限公司 | Blockchain transaction method, apparatus and device, and computer readable storage medium |
| CN115129988A (en) * | 2022-06-29 | 2022-09-30 | 北京达佳互联信息技术有限公司 | Information acquisition method and device, electronic equipment and storage medium |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101620703A (en) * | 2008-07-04 | 2010-01-06 | 阿里巴巴集团控股有限公司 | Buffer bookkeeping method and device |
| CN101989213A (en) * | 2009-08-07 | 2011-03-23 | 阿里巴巴集团控股有限公司 | Account concurrent processing method and account concurrent processing system |
| CN101996382A (en) * | 2009-08-31 | 2011-03-30 | 中国工商银行股份有限公司 | System and method for solving hot account of bank agent product transaction |
| WO2014107989A1 (en) * | 2013-01-09 | 2014-07-17 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for determining hot user generated contents |
| CN103970599A (en) * | 2014-05-29 | 2014-08-06 | 中国银行股份有限公司 | Data processing method and device based on multi-process concurrence |
| CN105844521A (en) * | 2016-03-22 | 2016-08-10 | 中国银行股份有限公司 | Transaction concurrence quantity control method and device |
| CN105869043A (en) * | 2015-01-19 | 2016-08-17 | 阿里巴巴集团控股有限公司 | Disperse hot spot database account transfer-in and transfer-out accounting method and device |
| CN106529962A (en) * | 2016-11-18 | 2017-03-22 | 中国银联股份有限公司 | Method and device used for enhancing hotspot account processing ability in trading system |
| CN107016604A (en) * | 2017-02-22 | 2017-08-04 | 阿里巴巴集团控股有限公司 | Buffer method, device and the equipment of book keeping operation |
| CN107146075A (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | Request processing method and device |
| CN107274162A (en) * | 2017-05-31 | 2017-10-20 | 深圳市长亮科技股份有限公司 | A kind of processing method of high transaction concurrency |
-
2017
- 2017-10-27 CN CN201711020188.6A patent/CN107767264A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101620703A (en) * | 2008-07-04 | 2010-01-06 | 阿里巴巴集团控股有限公司 | Buffer bookkeeping method and device |
| CN101989213A (en) * | 2009-08-07 | 2011-03-23 | 阿里巴巴集团控股有限公司 | Account concurrent processing method and account concurrent processing system |
| CN101996382A (en) * | 2009-08-31 | 2011-03-30 | 中国工商银行股份有限公司 | System and method for solving hot account of bank agent product transaction |
| WO2014107989A1 (en) * | 2013-01-09 | 2014-07-17 | Tencent Technology (Shenzhen) Company Limited | Method and apparatus for determining hot user generated contents |
| CN103970599A (en) * | 2014-05-29 | 2014-08-06 | 中国银行股份有限公司 | Data processing method and device based on multi-process concurrence |
| CN105869043A (en) * | 2015-01-19 | 2016-08-17 | 阿里巴巴集团控股有限公司 | Disperse hot spot database account transfer-in and transfer-out accounting method and device |
| CN107146075A (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | Request processing method and device |
| CN105844521A (en) * | 2016-03-22 | 2016-08-10 | 中国银行股份有限公司 | Transaction concurrence quantity control method and device |
| CN106529962A (en) * | 2016-11-18 | 2017-03-22 | 中国银联股份有限公司 | Method and device used for enhancing hotspot account processing ability in trading system |
| CN107016604A (en) * | 2017-02-22 | 2017-08-04 | 阿里巴巴集团控股有限公司 | Buffer method, device and the equipment of book keeping operation |
| CN107274162A (en) * | 2017-05-31 | 2017-10-20 | 深圳市长亮科技股份有限公司 | A kind of processing method of high transaction concurrency |
Non-Patent Citations (1)
| Title |
|---|
| 吴晓晖: "浅谈解决电大在线高并发网站架构方案", 《科技致富向导》 * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110298746A (en) * | 2019-07-04 | 2019-10-01 | 中国工商银行股份有限公司 | Hot spot account concurrent data processing system and method |
| WO2021052098A1 (en) * | 2019-09-18 | 2021-03-25 | 深圳前海微众银行股份有限公司 | Blockchain transaction method, apparatus and device, and computer readable storage medium |
| CN110716794A (en) * | 2019-10-14 | 2020-01-21 | 网银在线（北京）科技有限公司 | Information processing method, device, system and readable storage medium |
| CN111008828A (en) * | 2019-12-28 | 2020-04-14 | 辽宁振兴银行股份有限公司 | Intelligent identification method for hot account of online transaction system |
| CN111008828B (en) * | 2019-12-28 | 2023-09-05 | 辽宁振兴银行股份有限公司 | Intelligent identification method for hot account of online transaction system |
| CN111461864A (en) * | 2020-03-31 | 2020-07-28 | 中国银行股份有限公司 | Transaction processing method and device |
| CN115129988A (en) * | 2022-06-29 | 2022-09-30 | 北京达佳互联信息技术有限公司 | Information acquisition method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107767264A (en) | Online transaction system focus account trading flow pressure real-time monitoring method and device | |
| CN109271435B (en) | Data extraction method and system supporting breakpoint continuous transmission | |
| US7739268B2 (en) | Optimization of performing query compilations | |
| Barker et al. | " Cut me some slack" latency-aware live migration for databases | |
| US8117415B2 (en) | Storage device estimating a completion time for a storage operation | |
| CN103023984B (en) | Terminal application server and application log filtering method thereof | |
| CN106469087B (en) | Metadata output method, client and metadata server | |
| CN106325984B (en) | Big data task scheduling device | |
| CN100538646C (en) | A kind of method and apparatus of in distributed system, carrying out the SQL script file | |
| US8583608B2 (en) | Maximum allowable runtime query governor | |
| US20160154866A1 (en) | Efficient data manipulation support | |
| Balmau et al. | Silk+ preventing latency spikes in log-structured merge key-value stores running heterogeneous workloads | |
| WO2021104383A1 (en) | Data backup method and apparatus, device, and storage medium | |
| CN104504147A (en) | Resource coordination method, device and system for database cluster | |
| Petrov et al. | Adaptive performance model for dynamic scaling Apache Spark Streaming | |
| CN101556597B (en) | Self-adaptive optimistic concurrency control method | |
| Yu et al. | {ADOC}: Automatically Harmonizing Dataflow Between Components in {Log-Structured}{Key-Value} Stores for Improved Performance | |
| CN112363812B (en) | Database connection queue management method based on task classification and storage medium | |
| US8533219B2 (en) | Adjusting one or more trace filters in a database system | |
| CN108897776A (en) | A kind of arithmetic processing method of data information, device and computer storage medium | |
| CN112925807A (en) | Database-oriented request batch processing method, device, equipment and storage medium | |
| US20040172408A1 (en) | Real time maintenance of a relational database priority | |
| CN113986840A (en) | Block chain data multilevel storage and reading method and storage system | |
| CN111176938A (en) | System running state monitoring method and device | |
| CN110007899B (en) | Storm-based universal window frame system |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180306 |
|
| RJ01 | Rejection of invention patent application after publication |