Abstract
The overwhelming increase of population will lead to an increase network traffic usage. In most products, local cache mechanism is implemented for the purpose of reducing the network traffics. However, Due to storage space limitations, lot of times, cache will get purged when there are lots of queries sent and replaced by other newest queries. It is not an efficient by using traditional methodology to build or forming cache. In order to reduce the network traffic usage, the paper propose a solution, which utilizes data mining technique with clustering concept, by gathering the current feedback data that have from our SPN (Smart Protection Network). we are able to form these data in groups with similarity, and by deploying these data to client side, to achieve the reduction of traffic usage. In prototype, this design can really reduce network traffic more than 8%.
Highlights
The cathe optimization method with innovation technology over the cloud technology [4], [7]–[10], [45]–[58], or known as the SPN (Smart Protection Network)
We collect all access logs from t0 to t1, utilize data mining technique [23]–[25], [30], [40] and clustering concept, by gathering the current feedback data we have from our SPN, we are able to form these data in groups with similarity, and by deploying these data to client side on t1, compare the original traffic volume from t1 to t2, and we can do the performance evaluation
In most of the SPN products, local cache mechanism is implemented for the purpose of reducing the network traffics
Summary
The cathe optimization method with innovation technology over the cloud technology [4], [7]–[10], [45]–[58], or known as the SPN (Smart Protection Network). If the group were downloaded all at once to a user computer as a pre-fetch cache in accordance with the present invention than all of the CRC entries within circle 604 would be downloaded and would contribute to a certain level of network traffic volume. Since the volume of network traffic created using the pre-fetch cache approach (area under line 614) is greater than the user query volume traffic created without deploying the pre-fetch cache (area under dashed line 618), it is advisable not to deploy this group as a pre-fetch cache In this situation, it is possible to remove a certain number of CRC entries from group 604 and to perform the calculations again. Once each client computer has received its pre-fetch cache and is processing suspect files and sending out new queries to the backend servers over the Internet, it is possible to begin the process again of obtaining an updated access log from that point in time and reiterating the steps.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
