Virtual Event Resource Prefetching for Network Contention
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
Implement client-side caching, load balancing, and distributed data push techniques to mitigate network resource contention, including prefetching database artifacts and static event display resources, caching them before the event, and transmitting minimal network responses to client devices.
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 can obtain the event data they need, 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. When the event begins, these pre-fetched resources are already available in the network edge cache, allowing clients to access them immediately without causing simultaneous backend database queries. This preliminary preparation resolves the contradiction by ensuring resource availability while avoiding the time penalty of real-time data retrieval from overloaded backend systems.
2Productivity
If the system prefetches and caches database artifacts and static resources for all upcoming virtual events, then network load during events is reduced, but network edge cache memory is consumed
Solution Approach 1:
The system applies partial action by selectively prefetching only the types of resources that are most beneficial to cache—specifically database artifacts and static event display resources—rather than all possible resources. The push-to-cache operation also implements partial action by pushing resources to only those client devices that have registered for the event, not to all clients universally. This selective approach reduces network edge cache memory consumption while still achieving significant network load reduction during events.
Solution Approach 2:
The system changes the parameter of resource caching from a static, all-or-nothing approach to a dynamic, event-driven approach. Resources are cached based on event timing parameters (prefetching when events are upcoming but not started) and client registration parameters (pushing only to registered clients). This parameter-based control allows the system to optimize the balance between network load reduction and cache memory consumption adaptively.
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.