Smart Resources

1. Introduction: Autonomous Resource Management

Smart Resources functions as the "brain" of the browser, running in the background and analyzing system load in real-time. Its primary goal is to provide maximum priority to the tab currently in active use, preventing unused tabs from consuming system resources.

2. Technical Architecture: Autonomous Tab Throttling

Unlike traditional browsers, the system uses a dynamic and autonomous throttling mechanism instead of static rules:

  • Dynamic Resource Allocation: CPU usage of background tabs is automatically reduced based on the importance of that tab and the user's past interactions.
  • Smart RAM Offloading: Tabs that have not been interacted with for a long time are put into "sleep" mode without data loss, freeing up space on the RAM.
  • Prioritization Engine: Tabs playing video, outputting audio, or performing active data transfers are marked as "critical resources" and excluded from throttling.

3. Security and Performance Integration

Smart Resources works in full harmony with other features in the Obside ecosystem:

  • Hyper Fetch Compatibility: While downloading large files, Smart Resources allocates dynamic bandwidth and CPU power to the Hyper Fetch download engine without slowing down the rest of the system.
  • Download Security Integration: During RAM-buffered scans, it temporarily transfers resource priority to the security engine to ensure the system remains responsive.
  • Network Efficiency: By minimizing the network activities of background tabs, it ensures the active tab has the highest possible internet speed.

4. Technical Advantages

  • System Stability: Reduces the risk of browser crashes and provides high-performance browsing even on low-spec devices.
  • Low Energy Consumption: Extends the battery life of laptops by optimizing CPU usage.
  • Latency Minimization: Minimizes the response time to user clicks and scrolling movements in the active tab.

5. Vision

Obside Smart Resources is based on the principle that the browser should not be a burden on the system, but a layer that accelerates it. It aims to provide a smooth experience even in the heaviest web applications while protecting the user's hardware.