Virtual Event Resource Caching for Network Contention Mitigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Virtual events experience network resource contention when multiple attendees simultaneously access network resources at the start or during the event, leading to overload and unacceptable interactive response times.
Innovation Solution
Implementing client-side caching, load balancing, and distributed caching techniques to mitigate network resource contention, including prefetching database artifacts and static event display resources, using client-side caches, and providing minimal network responses to reduce the load on backend systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple network clients simultaneously access network resources at the start of a virtual event, then all clients receive the event data, but network resources become overloaded and response times become unacceptable
Solution Approach 1:
The system performs preliminary actions by prefetching database artifacts and static event display resources before the virtual event starts. This advance preparation ensures that when multiple clients simultaneously access resources at event start, the data is already available, preventing network overload and maintaining acceptable response times.
Solution Approach 2:
The system introduces intermediary caching layers (server-side caches and client-side caches) between the network resources and the clients. These intermediaries store event data locally, allowing clients to retrieve information without continuously querying the backend, thereby reducing network contention and improving response times.
2Productivity
If the system prefetches and caches database artifacts and static event display resources before the event, then network resource contention is reduced, but additional server-side processing and memory usage increase
Solution Approach 1:
The system extracts static event display resources and database artifacts from the main network resource pool and stores them in dedicated cache memory. This separation allows efficient serving of these resources without consuming network bandwidth during event access, while the extraction of only necessary data minimizes memory usage.
Solution Approach 2:
The system implements local quality by creating cache instances at multiple levels (server-side caches near the data source and client-side caches near the users). This distributed caching approach optimizes resource efficiency locally at each level while reducing the overall burden on central network resources.
3Loss of time
If the system pushes database artifacts and static event display resources to client-side caches, then real-time network requests are minimized, but network bandwidth consumption during the push increases
Solution Approach 1:
The system uses periodic action by pushing event data to client-side caches in scheduled batches before the event starts, rather than responding to individual client requests in real-time. This periodic data distribution spreads bandwidth consumption over time, avoiding peak network overload while ensuring clients have data available immediately when needed.
Data Source
AI summary
Media, methods, and systems are disclosed for mitigating network resource contention. Event scheduling details are received regarding one or more virtual events. In response to determining that an upcoming virtual event will begin within a predetermined time threshold, various steps are performed. First, a predicted number of event participants is determined. Next, database artifacts associated with the upcoming virtual event are prefetched. Then static event display resources are accessed prior to a start of the upcoming virtual event, and the database artifacts and the static event display resources are cached. A network protocol request to access network resources is received from a client device. The database artifacts and the static event display resources are pushed to a client-side cache associated with the client device, and a minimal network response is transmitted to the client device.