CN107800767A - A kind of access response management method, server and computer-readable recording medium - Google Patents
A kind of access response management method, server and computer-readable recording medium Download PDFInfo
- Publication number
- CN107800767A CN107800767A CN201710818841.7A CN201710818841A CN107800767A CN 107800767 A CN107800767 A CN 107800767A CN 201710818841 A CN201710818841 A CN 201710818841A CN 107800767 A CN107800767 A CN 107800767A
- Authority
- CN
- China
- Prior art keywords
- access
- access request
- time
- consuming
- server
- 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
- 230000004044 response Effects 0.000 title claims abstract description 78
- 238000007726 management method Methods 0.000 title claims abstract description 49
- 238000012545 processing Methods 0.000 claims abstract description 104
- 238000000034 method Methods 0.000 claims abstract description 45
- 230000008569 process Effects 0.000 claims abstract description 32
- 238000004891 communication Methods 0.000 claims description 16
- 238000012544 monitoring process Methods 0.000 claims description 4
- 239000000284 extract Substances 0.000 abstract description 7
- 238000009825 accumulation Methods 0.000 abstract description 5
- 230000007246 mechanism Effects 0.000 abstract description 2
- 238000002360 preparation method Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 10
- 230000008859 change Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 239000000243 solution Substances 0.000 description 4
- 206010033799 Paralysis Diseases 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000011156 evaluation Methods 0.000 description 3
- 239000002585 base Substances 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 239000003637 basic solution Substances 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000005236 sound signal Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5681—Pre-fetching or pre-delivering data based on network characteristics
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a kind of access response management method, server and computer-readable recording medium, easily occurs the problem of access request accumulation or collapse when facing high concurrent visit capacity for existing server, the access response management method of the present invention, preset memory locations are arrived into the access result storage of the complex time-consuming access request of the business logic processing of access interface in advance.When receiving time-consuming access request, directly extract access result from preset memory locations and responded.Abandon when receiving time-consuming access request, the interim mechanism for taking server process resource and doing business logic processing, avoided process resource and taken for a long time by time-consuming access request, the problem of causing other requests can not obtain processing.The present invention also provides a kind of server and computer-readable recording medium, in the case where service side process performance is certain, improves the disposal ability that server reply high concurrent accesses, improves the response speed and Consumer's Experience for each access request.
Description
Technical Field
The present invention relates to the field of computers, and more particularly, to an access response management method, a server, and a computer-readable storage medium.
Background
With the development of internet technology, the services provided by the internet are continuously abundant, and more comprehensive and convenient services are provided for the majority of users. Meanwhile, the number of users of each large website is increasing. This represents the achievement of the website operation on the one hand, but on the other hand, the performance of the server is constantly being examined, since the server must bear a great deal of access pressure. Especially, the daily number of the users of the large-scale portal sites popular with the users is almost exponentially increased. During busy periods, the concurrency of access to these web servers may be kept at a high level. For such high concurrency, the server will be at risk of paralysis at any time if there is no good coping strategy.
At present, the basic solution to cope with high concurrent access volumes is mainly proposed around several aspects: use high-performance servers, high-performance databases, efficient programming languages, and also high-performance Web containers. Needless to say, the server, the database server, the Web container, and the efficient programming language with excellent performance certainly contribute to improving the processing efficiency of the service side, thereby relieving the instantaneous pressure of the server. However, the performance improvement of the server, the database and the Web container depends on the development of the related technology, and under the current technical development degree, the space for improving the performance is extremely limited and basically reaches the bottleneck. Therefore, the performance of the service side can hardly be further improved at present; and changes in programming languages are less likely. At the same time, however, the number of users of the web site is continuously increasing, and the problem of high concurrency faced by the server side is becoming more serious.
Therefore, the existing solution cannot fundamentally improve the high concurrency phenomenon faced by the server, and therefore, a solution is urgently needed to be provided for solving the problem that access requests are easy to accumulate, and even the server is crashed or paralyzed and cannot work normally when the server is faced with high concurrent access amount in the prior art.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the access response management scheme is used for solving the problem that a server in the prior art is easy to have access request accumulation, even crash and paralysis and cannot work normally when facing high concurrent access amount, and aiming at the technical problem, the access response management method, the server and the computer readable storage medium are provided.
In order to solve the above technical problem, the present invention provides an access response management method, including:
judging whether the received access request is a time-consuming access request, wherein the time-consuming access request is an access request of which the service logic processing complexity of an access interface meets a preset condition;
if so, extracting an access result corresponding to the time-consuming access request from a preset storage position for access response, wherein the preset storage position stores the access result corresponding to each time-consuming access request in advance.
Optionally, before determining whether the received access request is a time-consuming access request whose service logic processing complexity satisfies a preset condition, the access response management method further includes:
determining time-consuming access requests according to the service logic processing process of the access interface corresponding to each access request and the access pressure of the access interface;
performing service logic processing on the time-consuming access request to obtain an access result;
and storing the access result of the time-consuming access request into the preset storage position.
Optionally, the determining a time-consuming access request according to the service logic processing process of the access interface corresponding to each access request and the access pressure of the access interface includes:
judging whether the visited frequency of an access request access interface exceeds a preset frequency or not, and judging whether slow data query is included in service logic processing of the access request access interface or not, wherein the slow data query is the operation of querying or jointly querying N tables with data quantity exceeding a preset threshold in a database, and N is more than or equal to 2;
and if the visited frequency of the access request access interface is determined to exceed the preset frequency and the business logic processing of the access interface comprises slow data query, determining that the access request is a time-consuming access request.
Optionally, the storing the access result of the time-consuming access request in a preset storage location includes: and storing the access result corresponding to the time-consuming access request into a distributed cache.
Optionally, the storing the access result corresponding to the time-consuming access request in a distributed cache further includes: and controlling at least one device in the distributed cache to back up the access result stored by the other device.
Optionally, if it is determined that the received access request is not a time-consuming access request, the access response management method further includes:
judging whether the access request is a current frequent access request or not;
and if so, extracting an access result corresponding to the frequent access request from the preset storage position to perform access response.
Optionally, if it is determined that the received access request is neither a time-consuming access request nor a frequent access request, the access response management method further includes: and performing service logic processing on the access request to obtain an access result and performing access response.
Optionally, after the extracting the access result corresponding to the time-consuming access request from the preset storage location and performing the access response, the method further includes:
monitoring data resources corresponding to the time-consuming access requests in a database;
and when the data resource corresponding to the time-consuming access request is determined to be changed, updating the access result corresponding to the time-consuming mode request in the preset storage position.
Alternatively to this, the first and second parts may,
further, the invention also provides a server, which comprises a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the steps of the access response management method as described in any one of the above.
Further, the present invention also provides a computer-readable storage medium storing one or more programs, which are executable by one or more processors to implement the steps of the access response management method as described in any one of the above.
Advantageous effects
The invention provides an access response management method, a server and a computer readable storage medium, aiming at the problem that in the prior art, when the server faces high concurrent access amount, the server is easy to generate access request accumulation or the server is crashed due to overlarge access pressure. When the time-consuming access requests are received, corresponding access results are directly extracted from the preset storage positions to carry out access response. The mechanism that when the time-consuming access request is received, the processing resource of the server is temporarily occupied to perform service logic processing to obtain the access result is abandoned, and the phenomenon that the processing resource of the server is occupied by the time-consuming access request for a long time, so that other access requests cannot be processed and are accumulated on the server side is avoided. The invention also provides a server and a computer readable storage medium, which not only fundamentally reduce the possibility of accumulation of access requests and crash of the server under the condition of certain processing performance of the service side, but also improve the high concurrent access capability of the server; meanwhile, time-consuming access requests and common access requests can be processed more quickly, so that the response speed of each access request is improved, and the access experience of a user is improved.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
fig. 1 is a flowchart of an access response management method according to a first embodiment of the present invention;
FIG. 2 is a schematic diagram of a display interface of the terminal;
FIG. 3 is a flow chart of a process of a server in the access preparation phase according to a second embodiment of the present invention;
fig. 4 is a schematic diagram illustrating storage of access results by devices of a distributed cache according to a second embodiment of the present invention;
fig. 5 is another schematic diagram illustrating storage of access results by devices of a distributed cache according to a second embodiment of the present invention;
fig. 6 is a schematic diagram illustrating still another storage of access results by devices of a distributed cache according to a second embodiment of the present invention;
fig. 7 is a flowchart of an access response management method according to a second embodiment of the present invention;
fig. 8 is a schematic hardware structure diagram of a server according to a third embodiment of the present invention;
fig. 9 is a schematic structural diagram of an access response management system according to a third embodiment of the present invention;
fig. 10 is a schematic hardware structure diagram of an alternative mobile terminal according to a third embodiment of the present invention;
fig. 11 is a schematic diagram of a hardware structure of an optional server for implementing embodiments of the present invention.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The first embodiment:
in order to solve the problem that the performance improvement speed of the server in the prior art cannot always meet the increase speed of the access amount, and thus the server is prone to request accumulation and crash down under a high concurrency condition, the present embodiment provides an access response management method to solve the above problem, please refer to fig. 1:
s102, judging whether the received access request is a time-consuming access request.
The access requests all have corresponding access interfaces, different access requests correspond to different access interfaces, and the same access request corresponds to the same access interface. For example, 10 users all initiate access requests for obtaining the topic popularity ranking list to the server through respective clients, and since the 10 access requests all aim to obtain the topic popularity ranking list, the access interfaces corresponding to the 10 access requests are the same. The access interface is not a physical interface, and for ease of understanding, the access interface may be understood as a business logic processing flow, i.e., a processing method for an access request. The processing schemes for the same access request are naturally the same, so the business logic processing flows are the same, and the access interfaces are the same.
In the related art, after the server receives the access request from the client, all the received access requests are treated identically to obtain the access result for performing the access response. It should be appreciated that there are a few access requests that access the business logic processing of the interface relatively simply. For example, a user "forwards" a topic at a client, after receiving a forwarding instruction of the user, a terminal with the client generates an access request according to the forwarding instruction of the user, and a request server can return a display interface of the converted topic to the client, as shown in fig. 2. The user can input the forwarding carrying language record of the user in the display interface of fig. 2 according to the requirement of the user. After the user inputs the information, clicking a confirmation button, the client generates an access request again, the access request carries relevant information confirmed to be forwarded, after the server receives the access request, the server issues forwarding of the user, returns a display interface used for representing successful forwarding to the client, and updates contents such as topics forwarded by the user. The access requests forwarded by the application and the access requests for content sharing or topic approval operations of the user, which are not listed here, are relatively simple in response processing, and because the business logic processing related to the access interface of the access requests is relatively simple, the time for returning the access result is relatively short. For the service logic of the access interface to process simple access requests, the response time of the server side is usually in milliseconds, so the response speed is high.
However, in addition to the access requests with simple business logic processing flow, some access interfaces corresponding to the access requests have complex business logic processing, for example, database query operations are involved, and when a database is queried, a multi-table-to-table query needs to be performed on a table with huge data volume. Generally, if a ranking list, a tag ranking, or the like is included in an access result corresponding to an access request of a user, the access interface business logic processing corresponding to the access request is complicated and the processing time is long: the time from receiving the access request to finishing the service logic processing to obtaining the access result may reach the second level, and even may reach 3-4 s under the condition of high server pressure. Because the processing time for these access requests is long, the processing resources of the server will be occupied by these access requests for a long time, and cannot be released, and naturally other access requests cannot be processed, so that the phenomenon that the server crashes because other access requests are not stacked continuously when the server performs service logic processing on these access requests which consume much time is likely to occur.
Generally, when an access request with complex processing of access interface service logic is processed, it takes a lot of time, so in this embodiment, an access request with the complexity of processing of access interface service logic satisfying a preset condition is referred to as a "time-consuming access request". As can be seen from the foregoing description, a large part of the reasons that a server is prone to down in the face of high concurrent access volumes are due to the long-term occupation of the server processing resources by time-consuming access requests. Therefore, if the time-consuming access requests can be processed without spending a large amount of processing time and processing resources when the server access pressure is relatively high, the time resources and the processing resources can be saved for processing other access requests, and the possibility that the access requests are accumulated on the service side to cause the server downtime is reduced to a certain extent.
Based on the above thought, the server in this embodiment may predetermine the time-consuming access request based on the complexity of the business logic processing in each access request access interface: and the access interface service logic processes the access requests with the complexity meeting the preset conditions as time-consuming access requests, processes the time-consuming access requests to obtain access results, and then places the access results into a preset storage position. After receiving an access request from a client, judging whether the received access request is a time-consuming access request, if so, executing S104; otherwise, executing S106, and processing the access request according to the normal response processing flow.
And S104, extracting an access result corresponding to the time-consuming access request from the preset storage position to perform access response.
If the server determines that the currently received access request is a time-consuming access request, the server can directly extract a corresponding access result from the preset storage location, and then perform access response on the access request. It should be understood that, if a plurality of clients simultaneously initiate the same time-consuming access request, for example, 15 users simultaneously initiate time-consuming access requests for obtaining a topic popularity ranking list at 10:01 am on 30.8.7.8.01, according to the scheme provided by this embodiment, after receiving the 15 access requests, the server determines that the access requests are all time-consuming access requests, and then may directly extract the corresponding access result from the preset storage location to respond. This process does not substantially take up too much time and processing resources of the server.
However, according to the conventional access response management scheme, the server needs to perform service logic processing on the 15 access requests respectively to obtain corresponding access results. That is, the same business logic processing process needs to be executed 15 times at the same time, and the process of acquiring the topic popularity ranking list needs the server to perform multi-table and multi-table query operation on a plurality of tables with huge data volume in the database, so the request of acquiring the topic popularity ranking list belongs to a time-consuming access request, and the business logic processing process is very complicated, so that the server may be unable to process other access requests at the same time. Worse still, the duration of the business logic processing process for the time-consuming access request is not short, and therefore, may result in the server not being able to process other access requests for a relatively long period of time. Other access requests (including access requests with simple business logic processing and access requests with complex business logic processing) reach the server continuously, so that the server is very easy to backlog the access requests.
Therefore, the access response scheme proposed by the present embodiment has significant advantages over the conventional processing scheme. In some examples of this embodiment, the predetermined storage location is a cache of the server. When the server determines that the access interface service logic corresponding to a certain access request is complex to process, the server can process the access request to obtain an access result, and the access result is put into a cache of the server side. In the user access stage, when the received access request is a time-consuming access request, the access result is directly extracted from the cache of the server side and returned.
It should be appreciated that time-consuming access requests are addressed because the server is ready for its access results before the client initiates access. Therefore, no matter how complex and long the service logic processing of the time-consuming access request access interface is, in this embodiment, after the server receives the time-consuming access request, the server can directly obtain the access result and immediately perform the access response, which greatly improves the access experience of the user when initiating the time-consuming access request.
And S106, performing service logic processing on the access request to obtain an access result and performing access response.
If the server determines that the received access request is not a time-consuming access request, the server can directly perform service logic processing on the access request according to a traditional processing scheme, and perform access response on the client after obtaining an access result.
It should be appreciated that the same access request is initiated at different times and the resulting access results may be somewhat different. For obtaining the access request of the topic popularity ranking list, the updating speed of the topic popularity is very fast, and the topic popularity ranking list of the last minute may be different from the topic popularity ranking list of the next minute. Since the access result of the time-consuming access request in the preset storage location is finally from the service logic processing of the data in the database, the server monitors the data resource corresponding to the time-consuming access request in the database. When the change of the related data resources is monitored, the service logic processing is carried out again to obtain a new access result, and the new access result is used for covering the original access result in the preset storage position, so that the client can obtain the correct access result in high real-time performance after initiating the time-consuming access request.
In the above example, the server monitors the database for a change in the data resource corresponding to the time-consuming access request, and updates the access result when the change is monitored. In another example of the embodiment, the server may also periodically update the access result of the preset storage location. Of course, the length of the period may affect the real-time performance of the access result: the longer the period, the worse the instantaneity of the access result, and conversely, the better the instantaneity of the access result. However, at the same time, the processing pressure on the server is different due to the different cycle lengths: the longer the update cycle, the less the burden on the server due to the time-consuming access request for updating the access result, whereas the more the server needs to spend time and processing resources frequently to perform the access result update process.
In the access response management method provided in this embodiment, time-consuming access requests that require a large amount of processing time and processing resources of a server for service logic processing are determined in advance, and access results corresponding to the time-consuming access requests are placed in a preset storage location. Therefore, when the server receives the time-consuming access request from the client, the access result corresponding to the time-consuming access request can be directly extracted from the preset storage position and returned to the client for access response. The problem that when the time-consuming access request of the receiving end client is received, a large amount of processing resources and processing time are temporarily occupied to process the time-consuming access request, so that other access requests cannot be processed in time and are accumulated on the server side is solved. The method is equivalent to the situation that the processing capacity of the server facing high concurrent access amount and the pressure resistance of the server are improved under the condition that the overall performance of the server is certain, the access response of the client can be timely responded, and the user experience is guaranteed.
Second embodiment:
the present embodiment will continue to explain the access response management method on the basis of the first embodiment. It should be understood that the access response management method in this embodiment is actually divided into two phases: one phase is the "access preparation phase" and the other is the "client access phase". The client access stage is naturally a stage of receiving an access request of the client and returning an access result to the client through a corresponding access interface; in the access preparation stage, it needs to determine which access requests access the service logic processing of the interface more complicated and belong to the time-consuming access requests, and then obtain the access results for the time-consuming access requests in advance, so as to avoid spending time and processing resources to process the time-consuming access requests in the client access stage. To facilitate understanding of the access response management method in this embodiment by those skilled in the art, the access preparation stage in the access response method is described below with reference to fig. 3:
s302, time-consuming access requests are determined according to the service logic processing process of the access interface corresponding to each access request and the access pressure of the access interface.
In the first embodiment, the server determines the time-consuming access request mainly according to the complexity of the business logic processing of each access request access interface. Optionally, when judging whether the business logic processing in one access request access interface is complex and meets the preset condition, the judgment may be performed by considering whether slow data query is included in the business logic processing through the access interface. The slow data query refers to an operation of querying or performing combined query on N tables with data quantity exceeding a preset threshold in a database, wherein N is greater than or equal to 2. It is needless to say that if a data query operation belongs to slow data query, in the data query, the database tables participating in the query must include two or more tables, and the total data amount of each table exceeds the preset threshold, or the data amount of each table exceeds the preset single-table data threshold. If the business logic processing of one access request access interface comprises slow data query, the complexity of the business logic processing of the access request access interface meets the preset condition. If the business logic processing of a certain access request access interface does not include slow data query, it means that even if the access request is received in the client access stage and then the processing is temporarily performed, too much time and too much processing resources are not spent, and the processing capacity of the server is not greatly influenced, so that the access request does not need to be taken as a time-consuming access request.
In contrast to the first embodiment, in the access preparation phase of this embodiment, the server considers two factors when determining whether an access request belongs to a time-consuming access request: one is whether the business logic processing procedure in the access interface of the access request is complex enough, and the other is whether the access pressure of the access interface of the access request is large enough. For the evaluation of the complexity of the business logic processing in the access request access interface, the evaluation can be made based on whether the business logic processing includes slow data query with reference to the above description. For the evaluation of access pressure of the access interface, a feasible scheme is proposed:
the access pressure of the access interface of the access request is mainly embodied by the access frequency of the access interface, if an access request is frequently initiated by each client within a period of time, the access frequency of the access interface of the access request is larger, that is, the access pressure of the access interface is larger. In this embodiment, the server may count the visited frequency of each access request access interface, and when the visited frequency of the access interface exceeds the preset frequency, it indicates that the access pressure of the access interface meets the condition.
If the access interface of a certain access request simultaneously meets the two conditions that the business logic processing is complex enough and the access pressure is large enough, the access interface can be used as a time-consuming access request by the server.
And S304, performing service logic processing on the time-consuming access request to obtain an access result.
In the access preparation phase, when the server determines that a certain access request is a time-consuming access request, although the access request from the client is not currently received, the server may also process the time-consuming access request in advance to obtain a corresponding access result.
S306, storing the access result of the time-consuming access request into a preset storage position.
After obtaining the access result, the server stores the access result of the time-consuming access request in a preset storage location, where in this embodiment, the preset storage location refers to a distributed cache on the server side. The distributed cache may be formed by two or more devices. In an example of this embodiment, the distributed cache is formed by A, B, C three devices together, and the server may divide the access results corresponding to all the time-consuming access requests into 3 shares, where the identifiers of the shares are a, b, and c; then, the server stores all the access results corresponding to a in the cache of the device a, stores all the access results corresponding to B in the cache of the device B, and stores all the access results corresponding to C in the cache of the device C, and a schematic diagram of the distributed caches for storing the access results is shown in fig. 4. It should be understood that, in this case, after the server receives an access request and determines that the access request is a time-consuming access request, before extracting its access result, it needs to further determine the storage location of the time-consuming access request corresponding to the access result.
Because the distributed cache device on the server side may have power failure, and the like, to avoid the problem that the access result of the cache is lost after the power failure or other failures occur to some devices in the distributed cache, and also to avoid the problem that the server cannot obtain the access result in a device when a certain device in the distributed cache fails to provide service, in an example of this embodiment, a solution idea is provided as follows:
when the server stores the access result of the time-consuming access request in the distributed cache, the server can control at least one device in the distributed cache to back up the access result stored by another device. Continuing with the example of the distributed cache device including A, B, C three devices, please refer to fig. 5: the device a originally stores the access result a, the device B originally caches the access result B, and the device C originally stores the access result C. In order to prevent the data originally stored on one of the three devices from being lost after a certain device of the three devices fails, the device a can back up the access result stored in the device B, the device B can back up the access result cached in the device C, and the device C can back up the access result cached in the device a. That is, the device a stores the result of the access a and the result of the access B, the device B caches the result of the access B and the result of the access C, and the device C caches the result of the access a and the result of the access C. Therefore, when one of the devices fails, the other two devices can continue to provide the cache service, and when the device recovers to normal, the access result originally cached by the device can be obtained from the other two devices.
This embodiment also provides a scheme for caching the access result of the time-consuming access request, please refer to fig. 6. In this example, each device in the distributed cache backs up the data cached on all other devices, that is, the access results of the caches on the devices in the distributed cache are the same. Continuing with the example that the distributed cache includes A, B, C three devices, when caching the access result of each time-consuming access request, the server may control device a to cache all the access results a, B, and C, control device B to cache all the access results a, B, and C, and similarly control device C to cache all the access results a, B, and C. This manner of being visited can be briefly described as: and backing up the access results cached by each device in the distributed cache.
The cache backup scheme shown in fig. 6 can ensure that when some devices in the distributed cache fail, other devices can still provide service to the outside without obstacles, and after the failed device recovers to normal, the device can obtain an access result of the original cache from any other device; meanwhile, in the cache backup scheme shown in fig. 6, since the access results cached by the devices are not different, and therefore the services provided by the devices are not different, after the server receives more time-consuming access requests within a period of time, addresses for extracting the access results can be allocated to the time-consuming access requests in a load balancing manner, so that the read-write pressure of the devices in the distributed cache device is ensured to be in a relatively balanced state, the optimal configuration of resources is facilitated, and the device is prevented from being crashed due to the fact that the pressure of part of the devices is too high.
In another example of this embodiment, in the access preparation phase, the server not only obtains and stores the access result of the time-consuming access request into the distributed cache, but also stores the access result of the "frequent access request" into the distributed cache in advance. The frequent access request in the present embodiment refers to an access request that is frequently initiated in the last period of time. The frequent access request is the access request which is frequently initiated recently, but the processing of the access interface service logic is not very complicated, namely the complexity of the processing of the access interface service logic does not meet the preset condition.
In the embodiment, the server determines the frequent access request in the access preparation phase, and stores the corresponding access result in the distributed cache. Similar to the time-consuming access request, after the server receives the frequent access request, the server also extracts the corresponding access result from the distributed cache and directly performs the corresponding operation. It is understood that the access results of the frequent access requests and the access results of the time consuming access requests may be stored together or separately.
After the access preparation phase is described, the access response management method in this embodiment is further described below with reference to the flowchart shown in fig. 7:
s702, judging whether the received access request is a time-consuming access request.
If the server finds that the received access request is a time-consuming access request by judging, S704 is executed, otherwise, S706 is executed. In an example of this embodiment, after determining the time-consuming access requests in the access preparation phase, the server may record identification information of each time-consuming access request, for example, store identification information corresponding to each time-consuming access request in the time-consuming request table. After receiving an access request sent by a client, determining whether identification information of the received access request is pre-recorded in a time-consuming request table, if so, indicating that the received access request belongs to the time-consuming access request, otherwise, indicating that the access request is not the time-consuming access request.
S704, extracting an access result corresponding to the time-consuming access request from the distributed cache to perform access response.
When the server determines that the received access request is a time-consuming access request, the server may directly extract a corresponding access result from the location where the time-consuming access request is stored in the distributed cache, and respond to the time-consuming access request.
S706, judging whether the access request is the current frequent access request.
If the server determines that the access request just received is not a time-consuming access request, the server may continue to determine whether it is a frequent access request, and if so, perform S708, otherwise perform S710. Similarly to determining whether the access request is a time-consuming access request, the server may record the identification information of each current frequent access request after determining the frequent access request in the access preparation phase, for example, store the identification information corresponding to each frequent access request in the frequent request table. After receiving an access request sent by a client, determining whether identification information of the received access request is prerecorded in a frequent request table, if so, indicating that the received access request belongs to a frequent access request, otherwise, indicating that the access request is not a frequent access request.
And S708, extracting the access result corresponding to the frequent access request from the distributed cache to perform access response.
When the server determines that the received access request is a frequent access request, the server can directly extract a corresponding access result from the position where the frequent access request is stored in the distributed cache, and respond to the frequent access request.
And S710, performing service logic processing on the access request to obtain an access result and performing access response.
If the server determines that the received access request is neither a time-consuming access request nor a frequent access request, the server may directly perform service logic processing on the access request to obtain an access result, thereby implementing a response to the access request.
Like in the first embodiment, the access results of the time-consuming access request and the frequent access request in this embodiment are not permanent, so the server needs to update the access results of the time-consuming access request or the frequent access request stored in the distributed cache at an appropriate time. In this embodiment, the update timing for the time-consuming access request may be determined by monitoring a change of a related data resource in the database, and when a change of a data resource corresponding to a certain time-consuming access request in the database is found, the time-consuming access request may be subjected to business logic processing again to obtain a corresponding access record, and an old access result in the distributed storage is updated and covered by using the new access result. And aiming at the frequent access request, the server can adopt a timing updating mode, namely, the server periodically updates, and after the period is reached, no matter whether the related data resources in the database are changed or not, the server performs corresponding service logic processing to obtain a new access result, so that the updating of the access result of the frequent access request in the distributed cache is completed.
As can be seen from the foregoing description, the two phases of access preparation and client access in this embodiment are actually for a single access request. That is, different access requests may be in different phases at the same time. For example, at a certain time T, access request X, is still in the access preparation phase, because the server is still counting the frequency of accesses to its access interface in order to determine whether it is a time consuming access request. But at the same time, the access request Y is already determined as a time-consuming access request, and possibly the server just receives the access request Y from a certain client, and extracts the access result of the access request Y from the cache for access response. Thus, in this embodiment, the time consuming access requests are not a fixed number of access requests: the partially time-consuming access request at time T1 may become a normal access request at time T2 because the frequency of subsequent accesses initiated by the client is not high; between the time T2 and the time T3, the server finds, through statistics, that there are some new access requests currently, which are not only lifted frequently, but also the service logic processing of the access interface is relatively complex, and these access requests may be normal access requests at the time T2, and become time-consuming access requests at the time T3.
The access response management method provided by this embodiment not only determines the time-consuming access request in the access preparation stage and stores the access result corresponding to the time-consuming access request in the distributed cache, and ensures that after the time-consuming access request is received in the client access stage, the complex business logic process can be avoided to directly obtain the access result, thereby saving processing time and processing resources, but also determines frequent access requests which are frequently lifted by the server, and puts the access results into the distributed cache, thereby ensuring access interfaces of the frequent access requests, and even when a large access pressure is encountered, the access response can be quickly completed, and the access experience of the user is improved.
Furthermore, in this embodiment, the server uses the distributed cache to store access results of the time-consuming access request and the frequent access request, and it is ensured that at least one device in the distributed cache backs up the access result stored by another device, so that it is ensured that after a part of devices in the distributed cache fails, the originally cached data can be recovered by other devices; meanwhile, after partial equipment fails, the storage and extraction service of the access result can be provided by the rest equipment, and the stability and reliability of the cache at the server side are improved.
The third embodiment:
the present embodiment first provides a computer-readable storage medium, in which one or more computer programs are stored, and the computer programs can be read, compiled and executed by a processor, so as to implement corresponding method flows. In the present embodiment, a computer program that can implement the access response management method in the foregoing embodiments is stored in a computer-readable storage medium.
In addition, the present embodiment further provides a server, please refer to fig. 8, in which the server 80 includes a processor 81, a memory 82, and a communication bus 83. Wherein the communication bus 83 is used for realizing the connection communication between the processor 81 and the memory 82, the memory 82 is a computer-readable storage medium in which an access response management program is stored, and the processor 81 can realize the access response management method described in the foregoing embodiments by executing the computer program.
For a specific process of the processor 81 of the server 80 to implement the access response management method in the foregoing embodiment, please refer to the description of the foregoing embodiment, which is not described again in this embodiment. It is understood that the access strong management method in the foregoing embodiment may also be implemented by a service background including multiple servers. Wherein the distributed cache may be deployed on a plurality of individual servers and the database may also be deployed in the memory of a plurality of servers.
The present embodiment further provides an access response management system, as shown in fig. 9: the access response management system 9 includes a service backend 90 and a plurality of clients 93. The access response management method in the foregoing embodiment is performed by a service back-office 90 including a first server 91 and a second server 92, and the service back-office 90 may provide access services for a plurality of clients 93. The client 93 described herein may be deployed on various terminals, for example, mobile terminals such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and fixed terminals such as a Digital TV, a desktop computer, and the like. In the following description, the client 93 is described as being deployed on a mobile terminal, and those skilled in the art will understand that the client 93 mentioned in the embodiments of the present invention may also be deployed on a fixed type terminal.
The construction of the mobile terminal in which the client is disposed will be briefly described below with reference to fig. 10, and in the following description, suffixes such as "module", "means", or "unit" used to represent elements are used only for the convenience of description of the present invention and have no particular meaning in themselves. Thus, "module", "component" or "unit" may be used mixedly.
In order to implement the hardware structure diagram of the mobile terminal according to the embodiments of the present invention, the mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an a/V (audio/video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a first memory 109, a first processor 110, and a power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture illustrated in fig. 10 is not intended to be limiting of mobile terminals, and that a mobile terminal may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components.
The radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the received downlink information to the first processor 110; in addition, the uplink data is transmitted to the base station. WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 10 illustrates WiFi module 102, it is understood that it does not belong to the essential components of the mobile terminal.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the first memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like.
The a/V input unit 104 is used to receive audio or video signals. A/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors.
The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 107 may include a touch panel 1071 and other input devices 1072. Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation on or near the touch panel 1071, the touch panel may transmit the touch operation to the first processor 110 to determine the type of the touch event, and then the first processor 110 may provide a corresponding visual output on the display panel 1061 according to the type of the touch event. Although in fig. 10, the touch panel 1071 and the display panel 1061 are two independent components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.
The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.
The first memory 109 may be used to store software programs as well as various data. The first memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the first memory 109 may include a high speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The first processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by running or executing software programs and/or modules stored in the first memory 109 and calling data stored in the first memory 109, thereby performing overall monitoring of the mobile terminal. The first processor 110 may include one or more processing units; preferably, the first processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the first processor 110.
The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the first processor 110 through a power management system, so as to manage charging, discharging, and power consumption management functions through the power management system.
Although not shown in fig. 10, the mobile terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.
Since the first server 91 and the second server 92 in the service background 90 may adopt the same structure, the structure of the first server 91 will be described in detail with reference to fig. 11:
the first server 91 includes at least: an Input Output (IO) bus 911, a second processor 912, a second memory 913, a memory 914 and a communication device 915. Wherein,
an input/output (IO) bus 911 is connected to and provides a transmission line for other components (the processor 912, the storage 913, the memory 914, and the communication device 915) of the first server 91 to which the IO bus 911 belongs.
The second processor 912 generally controls the overall operation of the first server 91 to which it belongs. For example, the second processor 912 performs operations such as calculation and confirmation. The second processor 912 may be a Central Processing Unit (CPU).
The communication means 915, typically comprising one or more components, allows radio communication between the first server 91 to which it belongs and the wireless communication system or network.
The second memory 913 stores processor-readable, processor-executable software code containing instructions for controlling the second processor 912 to perform the functions described herein (i.e., software-executing functions).
In the access preparation stage, the first server 91 determines that part of the access requests are time-consuming access requests by evaluating the service logic processing complexity of the access interface corresponding to each access request and the access pressure of the access interface: for example, an access request for obtaining a topic popularity ranking list, an access request for obtaining a ranking list under each label, and the like. For these time-consuming access requests, the first server 91 performs service logic processing on the requests in advance to obtain corresponding access results, and stores the access results in the distributed cache of the service background 90. It should be understood that the device for caching the access result of the time-consuming access request in the service backend 90 may include not only the first server 91 and the second server 92, but also other devices.
When a user sends a relevant operation instruction through the user input unit 107 of the mobile terminal 100, for example, the user performs a topic popularity ranking list refreshing operation, the first processor 110 generates an access request for obtaining the topic popularity ranking list according to the operation instruction received from the user input unit 107, and controls the radio frequency unit 101 to send the access request to the first server 91. It should be understood that the first processor 110 may also control the WiFi module 102 to send the access request to the first server 91 if the user is currently in a WiFi environment.
After receiving the access request from the mobile terminal 100 through the communication device 915, the second processor 912 of the first server 91 finds that the access request is an access request for obtaining the topic popularity ranking list and belongs to a time-consuming access request, and therefore, the corresponding access result can be directly extracted from the distributed cache of the service background 90 for access response.
The server and the access response management system provided in this embodiment determine the time-consuming access request in the access preparation stage, and store the access result corresponding to the time-consuming access request in the distributed cache, so as to ensure that after the time-consuming access request of the client is received, a complex business logic process can be avoided to directly obtain the access result, thereby saving processing time and processing resources, improving the processing capability of the server, and improving user experience.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. An access response management method, characterized by comprising:
judging whether the received access request is a time-consuming access request, wherein the time-consuming access request is an access request of which the service logic processing complexity of an access interface meets a preset condition;
if so, extracting an access result corresponding to the time-consuming access request from a preset storage position for access response, wherein the preset storage position stores the access result corresponding to each time-consuming access request in advance.
2. The access response management method according to claim 1, wherein before determining whether the received access request is a time-consuming access request whose business logic processing complexity satisfies a preset condition, the access response management method further comprises:
determining time-consuming access requests according to the service logic processing process of the access interface corresponding to each access request and the access pressure of the access interface;
performing service logic processing on the time-consuming access request to obtain an access result;
and storing the access result of the time-consuming access request into the preset storage position.
3. The access response management method according to claim 2, wherein the determining a time-consuming access request according to the service logic processing procedure of the access interface corresponding to each access request and the access pressure of the access interface comprises:
judging whether the visited frequency of an access request access interface exceeds a preset frequency or not, and judging whether slow data query is included in service logic processing of the access request access interface or not, wherein the slow data query is the operation of querying or jointly querying N tables with data quantity exceeding a preset threshold in a database, and N is more than or equal to 2;
and if the visited frequency of the access request access interface is determined to exceed the preset frequency and the business logic processing of the access interface comprises slow data query, determining that the access request is a time-consuming access request.
4. The access response management method according to claim 2, wherein the storing the access result of the time-consuming access request in a preset storage location comprises: and storing the access result corresponding to the time-consuming access request into a distributed cache.
5. The method for access response management according to claim 4, wherein the storing the access result corresponding to the time-consuming access request in a distributed cache further comprises: and controlling at least one device in the distributed cache to back up the access result stored by the other device.
6. The access response management method according to claim 1, wherein if it is determined that the received access request is not a time-consuming access request, the access response management method further comprises:
judging whether the access request is a current frequent access request or not;
and if so, extracting an access result corresponding to the frequent access request from the preset storage position to perform access response.
7. The access response management method according to claim 6, wherein if it is determined that the received access request is neither a time-consuming access request nor a frequent access request, the access response management method further comprises: and performing service logic processing on the access request to obtain an access result and performing access response.
8. The access response management method according to any one of claims 1 to 7, wherein after the access response is performed by extracting the access result corresponding to the time-consuming access request from the preset storage location, the method further includes:
monitoring data resources corresponding to the time-consuming access requests in a database;
and when the data resource corresponding to the time-consuming access request is determined to be changed, updating the access result corresponding to the time-consuming mode request in the preset storage position.
9. A server, comprising a processor, a memory, and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the steps of the access response management method of any of claims 1 to 8.
10. A computer readable storage medium, storing one or more programs, which are executable by one or more processors to implement the steps of the access response management method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710818841.7A CN107800767A (en) | 2017-09-12 | 2017-09-12 | A kind of access response management method, server and computer-readable recording medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710818841.7A CN107800767A (en) | 2017-09-12 | 2017-09-12 | A kind of access response management method, server and computer-readable recording medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107800767A true CN107800767A (en) | 2018-03-13 |
Family
ID=61531755
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710818841.7A Pending CN107800767A (en) | 2017-09-12 | 2017-09-12 | A kind of access response management method, server and computer-readable recording medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107800767A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108696579A (en) * | 2018-04-28 | 2018-10-23 | 北京奇艺世纪科技有限公司 | A kind of request responding method, device and electronic equipment |
| CN109522124A (en) * | 2018-11-19 | 2019-03-26 | 郑州云海信息技术有限公司 | Storage management system loading method, device, equipment and readable storage medium storing program for executing |
| CN109660612A (en) * | 2018-12-11 | 2019-04-19 | 北京潘达互娱科技有限公司 | A kind of request processing method and server |
| CN110221777A (en) * | 2019-05-17 | 2019-09-10 | 上海新储集成电路有限公司 | A method of intelligence adjusts data center I/O access load |
| CN111224811A (en) * | 2019-10-31 | 2020-06-02 | 北京浪潮数据技术有限公司 | SNMP request monitoring system, method, device and computer readable storage medium |
| CN112784288A (en) * | 2021-01-22 | 2021-05-11 | 尚娱软件（深圳）有限公司 | Access management method, terminal, and computer-readable storage medium |
| CN113157425A (en) * | 2021-05-20 | 2021-07-23 | 深圳马六甲网络科技有限公司 | Service access processing method, device, equipment and storage medium |
| CN114327899A (en) * | 2021-12-29 | 2022-04-12 | 中国电信股份有限公司 | Method and device for responding to access request, nonvolatile storage medium and processor |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104123238A (en) * | 2014-06-30 | 2014-10-29 | 海视云（北京）科技有限公司 | Data storage method and device |
| CN104298675A (en) * | 2013-07-18 | 2015-01-21 | 国际商业机器公司 | Method and device for cache management |
| CN106844784A (en) * | 2017-03-14 | 2017-06-13 | 上海网易小额贷款有限公司 | Data cache method, device and computer-readable recording medium |
-
2017
- 2017-09-12 CN CN201710818841.7A patent/CN107800767A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104298675A (en) * | 2013-07-18 | 2015-01-21 | 国际商业机器公司 | Method and device for cache management |
| CN104123238A (en) * | 2014-06-30 | 2014-10-29 | 海视云（北京）科技有限公司 | Data storage method and device |
| CN106844784A (en) * | 2017-03-14 | 2017-06-13 | 上海网易小额贷款有限公司 | Data cache method, device and computer-readable recording medium |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108696579A (en) * | 2018-04-28 | 2018-10-23 | 北京奇艺世纪科技有限公司 | A kind of request responding method, device and electronic equipment |
| CN109522124A (en) * | 2018-11-19 | 2019-03-26 | 郑州云海信息技术有限公司 | Storage management system loading method, device, equipment and readable storage medium storing program for executing |
| CN109522124B (en) * | 2018-11-19 | 2021-12-17 | 郑州云海信息技术有限公司 | Storage management system loading method, device, equipment and readable storage medium |
| CN109660612A (en) * | 2018-12-11 | 2019-04-19 | 北京潘达互娱科技有限公司 | A kind of request processing method and server |
| CN110221777A (en) * | 2019-05-17 | 2019-09-10 | 上海新储集成电路有限公司 | A method of intelligence adjusts data center I/O access load |
| CN111224811A (en) * | 2019-10-31 | 2020-06-02 | 北京浪潮数据技术有限公司 | SNMP request monitoring system, method, device and computer readable storage medium |
| CN111224811B (en) * | 2019-10-31 | 2023-02-28 | 北京浪潮数据技术有限公司 | SNMP request monitoring system, method, device and computer readable storage medium |
| CN112784288A (en) * | 2021-01-22 | 2021-05-11 | 尚娱软件（深圳）有限公司 | Access management method, terminal, and computer-readable storage medium |
| CN112784288B (en) * | 2021-01-22 | 2024-05-10 | 尚娱软件（深圳）有限公司 | Access management method, terminal and computer readable storage medium |
| CN113157425A (en) * | 2021-05-20 | 2021-07-23 | 深圳马六甲网络科技有限公司 | Service access processing method, device, equipment and storage medium |
| CN113157425B (en) * | 2021-05-20 | 2024-05-03 | 深圳马六甲网络科技有限公司 | Service access processing method, device, equipment and storage medium |
| CN114327899A (en) * | 2021-12-29 | 2022-04-12 | 中国电信股份有限公司 | Method and device for responding to access request, nonvolatile storage medium and processor |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107800767A (en) | A kind of access response management method, server and computer-readable recording medium | |
| US11349940B2 (en) | Server side data cache system | |
| US20210226854A1 (en) | System and method of browsing offline and queried content | |
| KR102245025B1 (en) | Memory return method and device | |
| US10853329B2 (en) | Distributed file system | |
| CN107741937B (en) | Data query method and device | |
| CN113420051B (en) | Data query method and device, electronic equipment and storage medium | |
| EP2369494A1 (en) | Web application based database system and data management method therof | |
| US11586544B2 (en) | Data prefetching method and terminal device | |
| CN102449602A (en) | System and method for reducing startup cost of a software application | |
| US20150163280A1 (en) | Method and device for downloading file | |
| CN110740155B (en) | Request processing method and device in distributed system | |
| CN110737857A (en) | back-end paging acceleration method, system, terminal and storage medium | |
| CN105721538A (en) | Data access method and apparatus | |
| US20190306851A1 (en) | Operation mode switching method and user equipment | |
| CN109241031B (en) | Model generation method, model using method, device, system and storage medium | |
| CN115345464A (en) | Service order dispatching method and device, computer equipment and storage medium | |
| CN111367996B (en) | KV index-based thermal data increment synchronization method and device | |
| CN103729440B (en) | A kind of method and device of access website | |
| CN102567037B (en) | Realize the method that the timing of desktop material updates | |
| CN107239530A (en) | Label search method, device, system and computer-readable recording medium | |
| CN114710501B (en) | Service request processing method, device, server and computer readable storage medium | |
| Kumar et al. | Improve Client performance in Client Server Mobile Computing System using Cache Replacement Technique | |
| CN106445833A (en) | Reader-based picture display method and apparatus | |
| CN102790782B (en) | A kind of information processing method of microblogging and 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180313 |