Service Resource Optimization Strategy Explanation

This provides a detailed explanation of the AdGuardPrivate service resource optimization strategy, including improvements to the filter update mechanism, suggestions for optimizing parallel requests, and norms for using third-party lists, aimed at providing a more stable and reliable service experience.
Tags:
Categories:

Background Explanation

As the number of users grows and functional demands increase, we have observed that some high-resource-consuming configuration options may lead to service instability. To ensure service quality, we have conducted in-depth analysis and formulated corresponding optimization schemes.

Resource Optimization Strategies

1. Filter Update Mechanism Optimization

Current Situation Analysis

  • Some users have set the filter to update every hour
  • Each update requires a complete download-parse-duplicate removal process
  • International bandwidth limitations cause the update to take longer
  • Server resources remain under continuous high load

Optimization Scheme

We will adjust the update interval to a minimum of 72 hours for the following reasons:

  • Most filter lists have an update cycle of 24-72 hours
  • Reduce ineffective resource consumption
  • Ensure service stability
  • Optimize bandwidth usage efficiency

Impact Assessment

  • Positive Impacts
    • More stable service response
    • More reasonable resource usage
    • Reduced system load
  • Minimized Impacts
    • Rule updates still maintain a reasonable cycle
    • No impact on protective effects

2. Parallel Request Strategy

Current Situation

Currently, most users have enabled the parallel requests feature, but under the existing architecture, the benefits are limited:

  • Alibaba Cloud upstream service latency differences are usually within 5ms
  • May trigger request frequency limits for Alibaba Cloud public services
  • Increases unnecessary system overhead

Usage Suggestions

  • Recommend using the load balancing mode
  • Parallel requests are suitable for the following scenarios:
    • Significant upstream service latency differences (>200ms)
    • Situations with unstable service quality
    • Cross-border access scenarios

Note: Currently, no rate limiting issues due to parallel requests have been identified; this feature remains open for now.

3. Third-Party List Management

Security Considerations

To ensure system stability, we have temporarily disabled support for some third-party lists:

  • The scale of external lists is unpredictable
  • May lead to resource overruns
  • Service stability cannot be guaranteed

Future Plans

We are researching more secure third-party list management solutions to reopen this feature in the future.